An agent with thirty tables and ten tools answers worse than three focused agents plus one that knows whom to ask.
you
↓
Coordinator ← has no tables at all; knows how to route
↙ ↓ ↘
Sales Finance Operations ← each with its own tablesHow to build it#
In the agent's configuration, choose "Coordinates specialists" and check who joins the team.
Only published agents can join. Those that can't join appear in the list disabled with the reason:
- it's a supervisor — a supervisor inside a supervisor creates a hierarchy that no one can read later;
- it's a draft — it would answer with a definition no one has reviewed;
- it's the agent itself.
A coordinator without a specialist can't be published: it would be an agent that only knows how to say "I'll ask someone" and has no one to ask.
What happens when you ask#
The coordinator understands the subject, rewrites the question, and sends it to the specialist. The rewrite matters: the specialist doesn't see your conversation. If you wrote "what about the second one?", it receives "which state has the second-highest revenue?".
The answer always says who answered. A team answer without attribution is worse than an answer from a single agent — when it's wrong, there's nowhere to fix it.
Delegating doesn't expand permissions#
If you can't reprocess a pipeline, the coordinator can't get around that by asking a specialist who can. The permission is checked again at every hop, and it is always yours.
Limits#
| Limit | Value | Why |
|---|---|---|
| Depth | 2 | The specialist answers; it doesn't delegate again |
| Specialists per question | 3 | Each query is an AI call and costs money |
| Repeat the same one | no | If it has already taken part, it isn't called again |
Each query to a specialist appears separately in the cost — you see how much each one spent, instead of a single number.