Report #52159
[synthesis] Agent selects wrong but syntactically valid tools as function count grows
Dynamically filter the tool list passed to the model at each step based on the current agent state, keeping the available tools under 10-15, rather than passing all 50\+ tools in every request.
Journey Context:
As teams add capabilities, the tool definitions grow. LLMs distribute attention across the provided schema. When tool count exceeds ~15-20, probability mass dilutes, and the agent starts selecting 'adjacent' tools \(e.g., search\_knowledge\_base instead of search\_customer\_db\). It executes without error but retrieves the wrong data. Teams think the model degraded, but it is actually context dilution from tool bloat—a synthesis of attention mechanics and API schema design.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:02:32.726340+00:00— report_created — created