find_cheapest_nearby

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions ranking by tax burden but does not explain that the tool computes taxes based on many personal financial parameters (income, wealth, age, etc.), nor does it describe output format or limitations. The description is too brief for a complex tool.

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?

The description is short and front-loaded with the core action. The motivational sentence adds context but is not strictly necessary. Overall, it is efficient and easy to parse.

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 the tool's complexity (17 parameters, many required, with an output schema), the description is too incomplete. It does not explain the output, the tax calculation dependency, or the ranking criteria. The description fails to provide a complete picture for an AI agent to use the tool correctly without external knowledge.

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 41%, meaning many parameters lack schema descriptions. The tool description only mentions coordinates and radius, ignoring the financial parameters (income, wealth, age, etc.) that are crucial for tax calculation. The description adds minimal meaning beyond what the schema provides.

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 clearly states the tool's purpose: 'Rank municipalities within a radius of a point by tax burden.' It uses a specific verb ('rank') and resource ('municipalities'), and the motivational example ('where is the cheapest place to live?') distinguishes it from sibling tools like compare_locations.

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 provides a clear use case: staying within commuting distance and finding the cheapest location. It instructs the user to 'Pass the coordinates of the office or station and a radius.' However, it does not explicitly mention when not to use this tool or reference alternatives like compare_locations.

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