MENU
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?
The supplied Claude Certified Developer Foundations material identifies A as the best answer. The decision should begin with the actual capability gap rather than a predetermined preference for built-in or custom tooling. If the existing capability can satisfy the requirement with a small supported extension or composition, using it avoids unnecessary implementation and maintenance. If the missing capability is fundamental, a custom tool becomes justified.
Anthropic's tool architecture explicitly supports both categories. Claude provides Anthropic-managed or predefined tools while also allowing developers to define custom tools for operations specific to their application. With a custom client tool, the application defines the contract and executes the operation before returning its result to Claude.
A is more complete than C because it evaluates both sides of the boundary: whether the existing mechanism can realistically meet the missing requirement and, if not, whether custom implementation is warranted. B prioritizes precedent over current requirements. D only determines whether the unmodified built-in tool is sufficient and does not address what to do when it is almost---but not entirely---sufficient.
Relevant Claude Developer topics: built-in tools, custom tools, capability-gap analysis, tool contracts, maintenance cost, extensibility, and agent construction decisions.
===============
Currently there are no comments in this discussion, be the first to comment!