Operating steps
- Measure the current tools/list payload and schema token footprint.
- Create a first-pass index with tool names, one-line purposes, and routing hints.
- Move full input schemas, examples, and long descriptions behind on-demand manifests.
- Replay real traces to confirm agents can still select the correct tools.
Common risks
- Over-compressing tool descriptions can make routing ambiguous.
- Leaving examples in the eager catalog often hides most of the savings.
- Different clients may cache or prefetch tool metadata differently.