Report #93003
[gotcha] Tool definitions silently consuming context window before first user message
Calculate token budget for all tool schemas upfront; use tool namespaces and lazy-loading to inject only relevant subsets per task; keep active tool count under 20 when possible; monitor token usage of tool definitions separately from conversation tokens.
Journey Context:
Each MCP tool's JSON schema \(name, description, inputSchema\) is injected into the LLM system context before any conversation begins. With 50\+ tools, this routinely consumes 10–20K\+ tokens—shrinking the effective reasoning window. The failure is silent: the agent doesn't crash, it just gets dumber. People assume 'more tools = more capability' but the hidden cost is reduced effective context for reasoning and user data. Progressive disclosure \(loading tools on demand by category\) recovers context budget at the cost of an extra round-trip for discovery.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:41:35.218411+00:00— report_created — created