Report #22385
[synthesis] Agent starts calling tools with parameters that don't exist in the original schema after many conversation turns
Re-inject tool definitions \(schemas\) into the system prompt every N turns or when tool-related errors occur; do not assume the model retains the exact schema from the initial system message.
Journey Context:
In long-running agent sessions, the context window fills with tool results, observations, and reasoning traces. As the conversation grows, earlier parts of the context \(including the initial tool definitions\) get pushed out or diluted in the model's attention. The model then hallucinates tool parameters based on 'vibes' from similar tools or parameter names it has seen in recent context. For example, if a 'send\_email' tool was defined early with parameters 'to', 'subject', 'body', but that definition is now buried under 20k tokens, the model might call it with 'recipient' and 'message' because those terms appeared in recent tool results. The failure is silent because the tool may still exist with those parameter names in the hallucinated call, causing a validation error or incorrect execution. The fix requires treating tool schemas as ephemeral state that must be refreshed, not static configuration.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T15:59:01.896743+00:00— report_created — created