Loading content
One orchestrating agent calls other agents exactly like tools, hiding their internal logic and coordination behind a standard tool interface. Typical conditions for use: Specialists must be encapsulated; The main agent must retain absolute control. The central trade-off: Excellent encapsulation is achieved against limited independence for the sub-agents.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
With agents-as-tools, a higher-level agent exposes other agents as callable tools and delegates subtasks to them.
The pattern grew from extending tool-using language-model agents into multi-agent orchestration, where one agent invokes specialists through clearly described interfaces.
A project lead knows specialist capabilities, assigns work deliberately, and integrates results.
One agent uses other agents through defined inputs and outputs.
Delegation encapsulates specialist knowledge and keeps the main task manageable.
Descriptions, permissions, and return contracts constrain subagent calls.
The pattern supports modular agent systems with clear responsibilities and controlled delegation.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.