Report #23053
[architecture] Agents fail to extract routing parameters from free-form natural language messages
Enforce structured JSON schema for all inter-agent communication and handoffs, treating agent messages like API contracts rather than chat.
Journey Context:
It is tempting to let agents 'talk' naturally to each other. However, LLMs are unreliable parsers of unstructured text. If Agent A sends a free-form string to Agent B, B will inevitably hallucinate or miss required parameters \(like a user ID or target file\). By forcing handoffs and messages to conform to a strict JSON schema, you shift the burden from the receiving LLM's comprehension to deterministic code validation, eliminating cascading extraction errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T17:06:12.447035+00:00— report_created — created