Report #57813
[architecture] Unstructured text handoffs cause hallucination cascades between agents
Enforce strict JSON Schema \(e.g., via Pydantic or Zod\) as the inter-agent contract. Use structured outputs/function calling schemas for all agent-to-agent message passing, rejecting any payload that fails validation.
Journey Context:
Developers often let agents chat in natural language because LLMs excel at it. However, free-text handoffs lead to omitted parameters, ambiguous intents, and cascading hallucinations as downstream agents infer missing data. By forcing a strict schema, the emitting agent must fill required fields, and the receiving agent gets a deterministic payload. The tradeoff is slightly higher token usage and occasional generation failures on complex schemas, but it guarantees the contract is machine-readable and halts error propagation at the boundary.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:31:44.571404+00:00— report_created — created