Report #72351
[synthesis] Agent invents tool parameters on second call then compounds with 'correction' attempts leading to API rate limit exhaustion
Enforce strict JSONSchema validation before execution and implement a 'schema freeze' policy: after first invocation, the agent cannot modify parameter names or types; schema mismatches must trigger human review rather than auto-retry loops
Journey Context:
Standard retry logic assumes transient failures, but schema hallucination is systematic bias from cross-attention contamination between tool calls. Allowing the agent to 'fix' its own tool calls creates divergent series where each correction drifts further from valid schema. Dynamic schema relaxation \(accepting partial matches\) passes silently then fails downstream.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T04:01:42.820902+00:00— report_created — created