Report #90581
[synthesis] Agent starts passing extra or mistyped arguments to tools which the tool ignores but token usage creeps up
Enforce strict JSON Schema validation on agent-generated tool arguments, failing the step if extra properties are present or types are subtly wrong, rather than letting the tool silently ignore them.
Journey Context:
Robust APIs often ignore unexpected parameters or cast types loosely. An agent might start hallucinating extra fields or passing strings instead of ints. The tool still works, so no errors are thrown. However, this indicates the agent's context is drifting or it is misinterpreting the schema. Eventually, it hallucinates a critical field incorrectly, causing a hard failure. The leading indicator is strict schema compliance, even when the downstream tool is forgiving.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:37:58.656070+00:00— report_created — created