Report #8458
[gotcha] Tool definitions silently consume context window budget before any user message
Calculate the token cost of all tool definitions upfront. Use progressive disclosure: expose only a core set of tools initially, load additional tools on-demand when the task requires them. Keep tool descriptions concise and strip redundant fields from JSON schemas.
Journey Context:
Each tool's JSON schema, description, and parameter definitions are injected into the system prompt or context. With 50\+ tools, this can consume 5,000–10,000\+ tokens before any user message arrives. The model then has less context for reasoning and is more likely to select the wrong tool. People assume 'more tools = more capability' but the hidden cost is reduced reasoning capacity and worse tool selection accuracy. The degradation is non-linear: going from 10 to 20 tools hurts less than going from 30 to 40.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T05:36:51.963037+00:00— report_created — created