Delegation has shapes
There are two common ways to use another agent. A handoff transfers conversational control to a specialist. An agent-as-tool keeps the manager in control and calls the specialist for a bounded subtask.
The difference matters for UX, logging, guardrails, and context ownership. A handoff changes who owns the next response. An agent-as-tool returns a result to the manager, which still owns synthesis and user-facing tone.
When to hand off
Use handoffs when the specialist should take over the conversation: support routing, billing versus refunds, domain-specific intake, or any branch where the user should now be talking to the specialist.
Use agent-as-tool when the manager should synthesize outputs: research workers, code reviewers, translators, evaluators. The specialist returns a bounded answer; it does not own the whole session.
The route must be inspectable
Every handoff should leave a route reason, the source agent, the destination agent, and enough compact context for the specialist to continue without rereading the whole conversation. Otherwise multi-agent becomes theater with extra latency.