Explanation:
Orchestration pattern: Agent-as-tools; Context passed to specialists: Scoped claim data only.
The primary claims agent must retain task ownership and synthesize the final response, which is the defining property of the agents-as-tools pattern. The primary agent decides when to invoke each specialist, receives the specialist ' s result, and remains responsible for the overall conversation. Handoff orchestration would instead transfer control to another agent and therefore weaken the ownership requirement. Microsoft Agent Framework also makes it possible for the outer agent to pass only the arguments needed by the inner agent rather than sharing the entire conversation history automatically. That supports least-privilege context: each specialist receives only the claim fields required for its assigned work. Passing the whole claim or a shared transcript would unnecessarily expose data outside the specialist ' s domain. The selected combination therefore satisfies both control ownership and data minimization. The architecture should still be validated with representative end-to-end tests, but the selected component establishes the correct structural boundary first. Microsoft ' s AI-500 blueprint consistently favors explicit scopes, interfaces, and persistence or identity boundaries over prompt-only conventions.
Official Microsoft reference: Microsoft Agent Framework - Agents as tools