ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

AWS Engineering Blog: Five Anti-Patterns for Multi-Agent Systems and an Architecture Decision Tree

The AWS Machine Learning team posits that multi-agent coordination is fundamentally a distributed systems problem, proposing a layered decision framework of Tier 1 deterministic workflows and Tier 2 autonomous orchestration. The article identifies five cost-draining anti-patterns—the God Agent, Unbounded Iteration, Natural Language Contracts, Premature Multi-Agent, and Unguarded Customer Contact—and uses four manufacturing constraints—takt time, safety boundaries, edge data, and shift cycles—to illustrate how architectural choices impact reliability and cost.

2026-11-17 05:53 GMT+8

The reasons for failures in multi-agent system implementations are rarely the models themselves. An engineering practice article recently published on the AWS Machine Learning blog offers a core judgment: multi-agent coordination is a distributed systems problem, and most teams attempting it have not yet developed distributed systems instincts. The article cites research from Stanford HAI indicating that when coordination overhead exceeds benefits, two models collaborating may perform worse than running individually. A straightforward arithmetic illustrates the risk: ten steps each with 95% reliability yield only 59.9% end-to-end reliability; twenty steps drop to 35.8%. Every handoff of dependency multiplies risk exponentially.

Based on this premise, the article categorizes coordination patterns into two tiers. Tier 1 is deterministic control flow—paths defined by developers at build time, including sequential pipelines, conditional workflows, conditional routing, and parallel workflows. Tier 2 is model-determined paths at runtime—including plan-based orchestration, handoff patterns, conversation-driven patterns, and debate/consensus patterns. Tier 2 handles work where steps cannot be predefined, at the cost of higher token consumption, latency, and debugging difficulty. The practical advice is to start with Tier 1 by default, upgrading to Tier 2 only when subtasks dynamically emerge during the workflow.

Sign in / Sign up
ReadingResearchRadarInvestment framework

The article identifies five anti-patterns that seem reasonable at the design stage but cause uncontrolled costs or decision drift in operation. First is the God Agent: one agent holding over 15 tools via a single prompt, responsible for equipment efficiency analysis, PLC diagnostics, and maintenance; tool selection degrades as the number grows, making fault attribution difficult. The fix is limiting agents to five tools or fewer. Second is Unbounded Iteration: agents looping on 'try again' without a hard stop, where retries amplify coordination failures rather than fixing them; the fix is setting hard iteration ceilings and budget alarms linked to automatic stops in code, as models will not stop themselves. Third is Natural Language Contracts: free-text prose passed between agents without schemas, where phrases like 'may indicate wear' harden step-by-step into 'confirmed wear' and then into maintenance orders; drift occurs at the weakest tracing points between agents. Fourth is Premature Multi-Agent: tasks completable by one agent with tool groups are split into multiple agents, each adding non-linear coordination tax, with gains flattening around four. Fifth is Unguarded Customer Contact: agents triggering irreversible actions like emails, service access, or machine parameters directly without approval, allowing hallucinations to cross into the physical world and escalating liability from refunds to product liability.

The article presents four architecture choice questions: Does the task require actions beyond text generation? Is the solution path known in advance? Does the work require genuinely distinct expertise? Can the solution only emerge through exploration? The decision tree guides readers from these four questions to select the simplest architecture—if you can draw the control flow on a whiteboard, use Tier 1 first; upgrade to Tier 2 only when subtasks dynamically emerge during the process.

Using manufacturing as a lens, the article explains how four constraints alter the architectural arithmetic: production-line takt time means latency equals revenue loss, requiring latency budgets based on p99 rather than averages; safety has physical consequences, meaning agents should only observe, analyze, and recommend without executing actions, with safety constraints existing as external deterministic guardrails rather than embedded in prompts; data is generated at the edge with millisecond-decaying value, making hybrid edge-cloud the practical default; and agent lifecycles must align with shifts, accumulating working memory within shift windows and emitting handoff summaries at shift ends to avoid drift caused by unbounded context.

The article's final recommendation is to start with Tier 1 patterns and expand only after proving value. Most manufacturing use cases—shift handoff summaries, quality gate decisions, predictive maintenance—are well served by deterministic workflows. Autonomous orchestration is reserved for truly open-ended problems where subtasks are dynamically discovered during the process, because token volume grows with every agent, robot, and shift; tiered model selection, context compression, and edge-cloud distribution are the primary levers for reducing costs.

Sources

  • aws.amazon.comAmazon Web Services↗
Continue researching →