Report #17975
[gotcha] 50\+ tool definitions silently consume 15-25% of context window before first interaction
Implement progressive tool disclosure — load only relevant tool subsets per task. Use a tool-search meta-tool or category-based filtering to expose tools on demand rather than registering all tools at startup.
Journey Context:
Each tool definition \(name \+ description \+ input schema\) costs 100-500 tokens. With 50 tools, that is 5,000-25,000 tokens consumed before the agent does anything useful. This leaves less room for reasoning, multi-step tool chains, and large tool results. The common mistake is registering every available tool upfront 'just in case.' The tradeoff is between tool availability and reasoning capacity. Progressive disclosure — loading tools based on task context — preserves context for actual work while keeping tools accessible when needed. This requires a meta-tool or routing layer but pays dividends in agent accuracy and effective context depth.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T06:52:48.562551+00:00— report_created — created