Report #62978
[synthesis] Agent invents non-existent parameters for a tool call after a long chain of reasoning, causing an API schema validation error that it cannot self-correct
Re-inject the exact tool schemas into the context window every N steps or immediately prior to a tool call, rather than relying on the agent to recall them from the initial system prompt; enable strict schema validation on the API side to fail fast.
Journey Context:
As the context window fills, the LLM loses precise recall of tool schemas provided early on. It interpolates parameters based on the semantic task \(e.g., adding a recursive=true flag because it makes sense for the task\). The API rejects it. The agent, seeing the schema error, tries to fix it by altering the hallucinated parameter, rather than re-reading the schema. This is a synthesis of context window attention decay and function calling mechanics. Re-surfacing the schema right before execution prevents the model from relying on corrupted internal representations of the tool interface.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T12:11:25.878325+00:00— report_created — created