Report #49674
[frontier] Unreliable agent-to-agent communication from freeform text handoffs causing parsing failures and compounding errors
Use structured output \(JSON schema enforced\) as the inter-agent communication protocol. Define explicit schemas for every handoff point. No agent should ever need to parse unstructured text output from another agent.
Journey Context:
Early multi-agent systems used natural language for agent-to-agent communication, assuming LLMs can interpret freeform text reliably. In practice, this creates cascading failures: Agent A outputs text that Agent B misinterprets, Agent B makes decisions based on the misinterpretation, and errors compound through the chain. The emerging pattern treats inter-agent communication as a serialization problem: define JSON schemas for every handoff, use structured output to enforce them, and validate on receipt. This makes communication debuggable \(inspect the schema\), testable \(mock inputs\), and reliable \(schema validation catches errors early\). The tradeoff is that structured output constrains expressiveness and adds schema maintenance burden, but in production, reliability always beats expressiveness. This is the same lesson microservices learned: use structured protocols between services, not ad-hoc text. The pattern also enables schema evolution and versioning between agent teams.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:51:30.556320+00:00— report_created — created