CCDV-F practice question 4 of 10

The team is debating whether to build a new capability as a custom tool or to use an existing built-in tool that nearly covers the use case but lacks one specific feature. How would you decide?

Full set: 95 questions
Answer options
A: Evaluate whether the missing feature can be addressed by extending the built-in tool or warrants a custom tool, then choose accordingly. Correct answer
B: Identify whether the team has previously built similar custom tools and use those precedents to determine which approach is more consistent with the existing codebase.
C: Examine the custom tool option by scoping the implementation effort and determining whether the additional flexibility justifies the development and maintenance cost.
D: Review the built-in tool's documentation and assess whether its existing capabilities are sufficient to cover the use case without any modification or extension.
Correct Answer:
A. Evaluate whether the missing feature can be addressed by extending the built-in tool or warrants a custom tool, then choose accordingly.
Explanation

When deciding between a built-in tool and a custom tool for a near-fit use case, the most pragmatic architectural approach is to evaluate if the missing functionality can be achieved by extending or wrapping the existing built-in tool. Anthropic’s tool use best practices emphasize keeping tools focused and minimizing unnecessary complexity. If the missing feature can be cleanly integrated as an extension or a complementary tool, it saves development overhead. However, if the workaround introduces excessive complexity or degrades the LLM's reasoning reliability, building a dedicated custom tool is warranted. This approach balances efficiency with optimal model performance.

Why Incorrect

B: Relying solely on historical precedents ignores the specific technical requirements and constraints of the current use case, potentially leading to suboptimal or forced tool design. C: While cost-benefit analysis is important, this option prematurely jumps to evaluating the custom tool without first considering if the built-in tool can be efficiently extended or adapted. D: This option is overly rigid; it assumes the built-in tool must be used exactly as-is and entirely dismisses the standard engineering practice of extending existing capabilities.

References

1. Anthropic Official Documentation: Tool use (function calling). Section: "Best practices for tool definitions" and "How to use tools". The documentation emphasizes scoping tools appropriately, minimizing redundant custom implementations, and ensuring tool interfaces are tailored to the model's capabilities. (Available at: https://docs.anthropic.com/en/docs/build-with-claude/tool-use)

2. MIT OpenCourseWare: 6.033 Computer System Engineering. Chapter 2: "Naming and Modularity". This courseware covers the fundamental architectural trade-offs of extending existing modules (built-in tools) versus building custom components from scratch to satisfy specific feature requirements. (Available at: https://ocw.mit.edu/courses/6-033-computer-system-engineering-spring-2018/)

3. Anthropic Official Documentation: Computer Use (Beta). Section: "Combining with other tools". This section illustrates how built-in tools (like the computer tool) can be augmented or extended by providing complementary custom tools to cover missing specific features in a workflow. (Available at: https://docs.anthropic.com/en/docs/build-with-claude/computer-use)

Scroll to Top