Report #81451
[architecture] Unstructured text passing between agents causes cascading hallucinations and parsing failures
Enforce strict JSON schema contracts at agent boundaries using structured outputs or function calling, treating inter-agent communication like an API contract.
Journey Context:
Developers often let agents chat in natural language because LLMs excel at it. However, NL is ambiguous. If Agent B expects a list of IDs and Agent A outputs a paragraph describing IDs, Agent B will guess or fail. Structured outputs force Agent A to compile its thoughts into a typed format, acting as a checksum on its reasoning. Tradeoff: slightly higher token cost and occasional generation failures if schema is too complex, but guarantees parseability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:19:00.527274+00:00— report_created — created