Home / Claude Certified Architect – Foundations / Objective 2.1

Domain 2: Tool Design & MCP Integration · 18% of the exam · Full exam outline

2.1 Design effective tool interfaces with clear descriptions and boundaries

What this objective covers

Tool descriptions as the primary mechanism LLMs use for tool selection; minimal descriptions lead to unreliable selection among similar tools. The importance of including input formats, example queries, edge cases, and boundary explanations in tool descriptions. How ambiguous or overlapping tool descriptions cause misrouting (e.g., analyze_content vs analyze_document with near-identical descriptions). The impact of system prompt wording on tool selection: keyword-sensitive instructions can create unintended tool associations. Writing tool descriptions that clearly differentiate each tool's purpose, expected inputs, outputs, and when to use it versus similar alternatives. Renaming tools and updating descriptions to eliminate functional overlap (e.g., renaming analyze_content to extract_web_results with a web-specific description). Splitting generic tools into purpose-specific tools with defined input/output contracts (e.g., splitting a generic analyze_document into extract_data_points, summarize_content, and verify_claim_against_source). Reviewing system prompts for keyword-sensitive instructions that might override well-written tool descriptions.

Practice questions

Question 1easy

An agent loads tools from a ticketing service and a wiki service. Both services expose a tool called 'search', and Claude sometimes queries the wrong system. Which naming change does the guidance recommend?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Version labels describe history, not purpose. Claude still cannot tell which tool reaches tickets and which reaches the wiki.

Every tool definition needs a name, and list order carries no meaning about what a tool does. Selection would get worse, not better.

This removes the name clash but not the ambiguity: a random suffix tells Claude nothing about which system each tool searches.

When tools span several services, the guidance recommends namespacing: prefix each name with its service. Two tools with the same vague name are exactly the overlap that confuses agents, and the prefix makes the boundary visible at selection time.

Question 2easy

A messaging tool has a required parameter named 'recipient'. Claude keeps passing people's display names, but the backend expects a numeric account identifier. Which change best addresses this?

Included in Master: master every domain.See plans