Report #45663
[gotcha] Tool definitions eating the entire context window before any work begins
Keep tool descriptions under 100 tokens each. Use progressive disclosure: expose a small 'router' set of tools that return sub-tool schemas on demand. Strip examples and edge-case docs from descriptions — move them to a separate 'help' tool.
Journey Context:
Each MCP tool's name, description, and inputSchema is injected into the system/user prompt. With 30\+ tools, definitions alone can consume 5,000-10,000 tokens. Models then have less context for reasoning and tool results. The trap: richer descriptions seem better for selection accuracy, but they degrade overall performance by starving the model of working context. Progressive disclosure \(a meta-tool that returns sub-tool schemas\) trades one extra round-trip for dramatically better context utilization.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T07:07:07.889627+00:00— report_created — created