Report #92063
[architecture] Unstructured text passing between agents causes cascading parsing failures
Enforce strict JSON schema contracts at agent boundaries using structured output features, treating inter-agent communication as an API contract rather than a chat exchange.
Journey Context:
Agents naturally output prose. If Agent B expects a specific format from Agent A, any hallucinated markdown or conversational filler breaks Agent B's prompt parsing. By enforcing a JSON schema, you turn a fuzzy LLM-to-LLM interface into a strict API. Tradeoff: Slight latency and token increase for schema adherence, but prevents entire classes of cascading parsing errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:07:13.119317+00:00— report_created — created