Report #61036
[architecture] Unstructured text passing between agents causes cascading parsing failures and hallucinated tool calls
Enforce strict JSON schema contracts at the boundary of every agent handoff, treating the output of Agent A as an untrusted API response to Agent B.
Journey Context:
Developers often let agents chat in natural language because LLMs excel at it. However, slight phrasing variations cause the receiving agent to miss key data or hallucinate missing fields. By forcing a strict schema, you shift the failure mode from a subtle semantic drift downstream to an immediate, catchable syntax error at the boundary. The tradeoff is slightly higher token usage and occasional refusals if the schema is too complex, but it guarantees machine-readable handoffs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:56:00.428004+00:00— report_created — created