CCAR-F practice › Tool Design & MCP Integration · Question 30 of 105
Tool Design & MCP Integration
A developer productivity agent has a web_search tool and an MCP code_search tool. Both have clear, distinct descriptions. The system prompt includes: "When the user asks you to search, use web_search to find the answer." Requests like "search the repo for callers of parseConfig" keep going to web_search. What is the most effective fix?
Show answer and explanation
Answer: B — Reword the system prompt instruction so "search" is no longer tied to web_search
The descriptions are already clear. A keyword-sensitive instruction in the system prompt links the word 'search' to web_search and overrides them. Rewording or removing that instruction fixes the cause (b). More description detail (a) can't outweigh a prompt that points the other way. Few-shot examples (c) add tokens to work around an instruction you control. Removing web_search (d) breaks legitimate web lookups.
Keep going
More Tool Design & MCP Integration questions
- A support agent's lookup_order tool wraps its database call in a catch-all that returns…
- An MCP tool calling an external catalog API sometimes gets "item not found" and…
- A process_refund tool rejects refunds above a $500 policy limit. The agent currently…
- In a research system, a document-fetch subagent sometimes gets HTTP 503 responses from a…
- Every subagent in a multi-agent research system was given the same 18 tools. Tool…