Report #1476
[gotcha] Tool schemas silently consume 20%\+ of context window with many MCP tools
Use MCP tools/list to discover tools, then filter to inject only the 5-10 most relevant tool schemas per task into the LLM context. Implement progressive disclosure: load tool groups on-demand based on task intent rather than injecting all schemas on every call.
Journey Context:
The instinct is to expose every capability so the model can do anything. But each tool's JSON Schema \(name, description, parameter definitions with descriptions\) costs 200-500 tokens. 50 tools × 400 average tokens = 20K tokens consumed before any user message. The LLM API does not warn you — it just silently has less room for reasoning and earlier context gets truncated. The model produces worse outputs with no obvious cause. People debug everything except the tool definitions themselves.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T23:31:31.646651+00:00— report_created — created