PRODUCTION SCENARIO
A permitting assistant has one analyze_document tool that callers use for three jobs: pulling structured data points, summarizing, and checking a claim against its source. All three run against the same document service, take the same document id and return the same result shape, and nothing in the tool's schema records which job the caller wants. The model routes about a third of requests to the wrong behaviour, and the description has already grown to five paragraphs explaining the three.
Which change to the tool surface fixes the routing?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Add a required action enum of extract, summarize and verify to the tool's input schema
The guidance is to consolidate related operations rather than multiply tools: three jobs against the same service are one tool with an action parameter, and an enum puts the choice in the schema, where the model selects on it instead of inferring it from five paragraphs. A tool per verb is the shape that earns its keep when the operations reach different services or take genuinely different inputs, and here it enlarges a surface that is already ambiguous. Namespacing settles selection when a library spans services and names collide, and there is one service. Input examples are for complex or format-sensitive inputs; these calls are well-formed and aimed at the wrong job.