find_location

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Given no annotations, the description carries full burden. It explains why tax_location_id is needed but does not disclose behavioral details such as whether multiple results can be returned, what happens if query is ambiguous, authentication requirements, or error handling. The schema shows a limit parameter implying multiple results, but description says 'resolve to' (singular), causing ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no fluff. First sentence states the primary purpose; second provides necessary context about why the result matters. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists (not shown), description need not detail return values. It covers essential purpose and motivation for using the tool. However, it lacks usage guidance and behavioral details, but overall is adequate for a lookup tool with clear purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (75%) and most parameters have descriptive explanations (limit, query examples, language enum, tax_year purpose). The description adds general context about the output being a tax_location_id but does not elaborate on individual parameters beyond the query. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the verb 'Resolve' and specifies the resource: a place name or postal code to an ESTV tax location id. It clearly distinguishes itself from sibling calculation tools by being a lookup tool for tax location IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing a tax location id from a place name, but does not explicitly state when to use or not use this tool compared to siblings like compare_locations or find_cheapest_nearby. No alternatives or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.