Report #13250
[tooling] Agent context window fills up with verbose MCP tool descriptions from OpenAPI specs
Aggressively compress tool descriptions to <200 tokens per tool by stripping examples and verbose explanations; store full schema in a 'documentation' resource referenced by the tool.
Journey Context:
Auto-generating MCP tools from OpenAPI specs creates descriptions that include every possible enum value, example requests, and 500-word explanations. Anthropic's tool use places these in the system prompt. A 20-tool server can consume 8k-10k tokens before any user message. The fix is to treat the tool definition as a 'signpost' \(short name, 1-sentence description\) and put the heavy schema in a resource that the agent can fetch only when needed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T18:15:35.519703+00:00— report_created — created