Skip to main content
    Monday, October 5, 2026

    Distribute tools appropriately across agents and configure tool choice

    Domain 2 — Tool Design & MCP Integration · 18% of the exam

    Task statement 2.3

    Distribute tools appropriately across agents and configure tool choice

    What you should be able to do
    • Explain why tool-selection reliability degrades as an agent's tool count grows.
    • Scope each subagent to the tools its role needs, with narrow cross-role exceptions for high-frequency cases.
    • Replace a general-purpose tool with a constrained one that validates its own inputs.
    • Use tool_choice "auto", "any" and forced selection, and say what each one guarantees.
    Exam traps (5)

    Give every agent the full toolset so none of them is ever blocked.

    Each additional tool widens the decision, so selection accuracy falls — and agents reach for tools outside their specialisation, like a synthesis agent running its own searches.

    Scope tools to the role. A blocked agent is a routing question for the coordinator, not an argument for a bigger toolbox.

    Set tool_choice to "any" so the model is guaranteed to pick the right tool.

    On configurations that support forcing, "any" requires some tool request, not a specific one. Models that reject forcing require a different integration.

    Check model compatibility: "any" requires some request and named selection constrains its identity. The application owns authorization and execution order.

    Force the required first tool and let the model handle the rest in the same turn.

    Forcing applies to the request you send it on, so the ordering guarantee does not extend across the steps that follow.

    On a supported model, require the first tool request, validate and execute it, then expose the next step. With auto, inspect the response before advancing.

    Route every cross-role need back through the coordinator, for cleanliness.

    A high-frequency check becomes a round trip through the hub every time, which dominates latency for something narrow and well-defined.

    Give a narrow scoped tool for the frequent case; route the complex ones through the coordinator.

    Keep a broad utility tool available because it covers many situations.

    A permissive tool accepts inputs it should refuse, so misuse shows up as plausible-looking output rather than an error.

    Prefer a constrained tool that validates what it is handed over a general one that will accept anything.

    Where the guide and the current docs differ (1)

    model-specific tool selection support (checked 2026-09-21)

    Answer this: Task 2.3 covers auto, any and forced tool selection.

    The docs now say: Claude Fable 5.1 rejects any and named selection. Use auto with strict tools and response checks, or structured outputs; selection, schema conformance and execution are separate controls. Read it

    Primary sources
    Know cold
    • Tool distribution
    • tool_choice
    • Least privilege
    • allowedTools

    15 practice questions in the bank are tagged to this task statement.

    Practise this task in context: open it inside the interactive study guide, which carries the concept cards, the mock quiz and the practice simulation.

    Blueprint-aligned independent practice. Koko's scenarios and company facts are fictional and synthetic. This aid does not reproduce official exam questions or Anthropic's undisclosed scoring model, and is not affiliated with or endorsed by Anthropic.