Report #11505
[architecture] Agents failing to parse inter-agent communications due to free-form natural language payloads causing hallucinated parameters
Enforce strict JSON schema for all inter-agent messages, reserving natural language strictly for a 'thought' or 'reasoning' field, never for action parameters or state updates.
Journey Context:
Developers often assume LLMs talking to LLMs should just use natural language since they are language models. However, free-form text introduces irreproducible parsing errors. Agent B reads Agent A's message and extracts the wrong file path or intent. Structured schemas act as a contract, making the system deterministic at the integration boundary. The tradeoff is a slight increase in prompt complexity and token usage, but it eliminates an entire class of parsing failure modes. This mirrors the shift from microservices using text/HTTP to gRPC/Protobufs for internal comms.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T13:35:36.933340+00:00— report_created — created