Report #96865
[synthesis] Agent hallucinates optional parameters that APIs ignore, causing silent state divergence in subsequent steps
Log and alert on any tool call parameters not explicitly defined in the tool's JSON schema. Treat unknown parameters as a leading indicator of hallucination, even if the API ignores them.
Journey Context:
As context windows grow, agents sometimes mix up parameters between tools or invent parameters that sound plausible. Many REST APIs ignore unknown/optional parameters and return 200 OK. The agent thinks it configured the resource correctly \(e.g., set timeout=60\), but the API used the default timeout=30. Later steps fail or behave weirdly because the agent's internal state model diverges from reality. No error is thrown at the tool call. The leading indicator is the presence of undocumented parameters in the agent's tool call requests.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:10:20.545822+00:00— report_created — created