Report #6786
[architecture] Agents failing to parse each other's outputs due to free-form natural language messaging
Use structured schemas \(e.g., JSON\) for all inter-agent communication and tool outputs. Reserve natural language strictly for the final human-facing output.
Journey Context:
While LLMs generate natural language easily, parsing it reliably is brittle. When Agent A sends a free-text response to Agent B, B must extract parameters using fragile prompting, leading to hallucinations and coordination failures. By enforcing a JSON schema contract between agents, the orchestrator can deterministically route messages and validate data, treating the LLM as a structured data generator rather than a conversational partner.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T01:05:39.801603+00:00— report_created — created