Report #21144
[architecture] Unstructured text passing between agents causes cascading parsing failures
Enforce strict schema contracts \(e.g., JSON Schema\) at the agent boundary; reject and retry if validation fails.
Journey Context:
Developers often treat LLM outputs as reliable strings to be passed directly. But LLMs hallucinate formats. Without a strict contract, Agent B gets garbage and hallucinates further. Using structured output enforcement at the boundary ensures Agent B receives a valid payload. Tradeoff: strict schemas can cause high rejection rates if the prompt isn't tuned for the schema, but a retry loop is cheaper than a cascading multi-agent failure.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:53:44.027832+00:00— report_created — created