Report #37713
[synthesis] Agent tool calls succeed but produce wrong behavior due to hallucinated JSON parameters
Enforce strict JSON Schema validation on tool inputs at the orchestrator level, rejecting any payload with extra or mistyped fields, even if the downstream API ignores them.
Journey Context:
APIs built with frameworks like FastAPI often silently ignore extra fields or coerce types. An agent might start hallucinating an override flag or adding conversational text into a strict parameter. The API returns 200 OK, so standard error monitoring sees success. However, the agent's intent was lost. Strict schema validation forces the LLM to retry and correct its output, making silent semantic drift a loud failure early on.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T17:46:51.988704+00:00— report_created — created