Fan-out looks like a speed decision and is actually a capacity decision. A sequential agent loop throttles itself — one request in flight, backpressure for free. The moment you dispatch fifty branches you have handed rate-limit management to the provider, and the provider manages it by refusing you. Three things to decide before you pick a library: how many run at once, what happens when one fails, and what you return when some succeed.
A handoff is not a message forward. Control does not return, so anything the caller knew and did not write down is gone the moment the transfer lands. OpenAI ships a filter to cut the trace, LangChain tells you to forward exactly two messages, and Google ADK isolates each subagent in its own session branch — three frameworks admitting the same thing. What travels across a handoff, and the three things that must never.
Anthropic measured its orchestrator-worker research system beating a single agent by 90.2%, while burning roughly 15x the tokens of a chat. Cognition spent a year telling people not to build multi-agent systems, then shipped one under a single rule: writes stay single-threaded. Three topologies, the failure mode each one owns, and the one you should default to.
Assigning agents roles and letting them converse is a genuinely useful abstraction for some problems and a determinism disaster for others. Meanwhile the most-cited framework in the category went into maintenance mode this year, which is its own lesson about what to depend on.