Report #57250
[agent\_craft] Agent confused by massive tool schemas consuming context window
Externalize tool schemas or use dynamic tool loading. Only inject the schemas for tools relevant to the current sub-task into the context.
Journey Context:
Providing an agent with 50\+ tool schemas \(e.g., entire AWS SDK\) consumes thousands of tokens and severely degrades the model's ability to select the right tool. Instead, provide a search\_tools function or a router that dynamically loads only the 3-5 relevant tool schemas needed for the current step into the LLM's context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T02:34:53.194683+00:00— report_created — created