Report #91116
[agent\_craft] Massive tool schemas consume context window and degrade tool selection accuracy
Implement dynamic tool loading. Only inject the schemas of tools relevant to the current sub-task into the prompt. Keep the active toolset minimal \(e.g., <10 tools\) and use a router or retriever to inject specialized tools on demand.
Journey Context:
Every tool definition consumes tokens and attention. A massive tool list creates noise, increasing the probability of the model selecting the wrong tool or hallucinating parameters. By using a two-step process—first selecting a category or toolkit, then loading its specific schemas—the agent maintains a high-accuracy, low-noise context. The tradeoff is an extra LLM call for routing, but the gain in reliability and context savings is worth it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:32:02.269477+00:00— report_created — created