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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context beyond annotations by specifying what results include and noting the premium API cost of $0.25 USDC via x402, which is a significant operational consideration.

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 two short sentences, with the core purpose front-loaded and the cost/payment note appended without adding noise. Every sentence adds value.

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?

The description explains the expected output scope and the cost, and with no output schema, it gives enough for an agent to decide and invoke the tool. It does not detail response structure or edge cases, but for a simple single-parameter read-only lookup this is acceptable.

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 100% for the single `lookup` parameter, which is already described as a 'Reference address or location'. The description reinforces this by saying 'address or location' but does not add substantial syntax or format guidance beyond the schema. 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 a specific verb and resource ('Find nearest coffee shops') and enumerates the returned details (names, addresses, distances, basic details). It is clearly distinct from all sibling Interzoid tools, which are other data lookup utilities.

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?

Clear context is provided: this tool is for finding coffee shops near an address or location. It does not explicitly state when not to use it or name alternatives, but its purpose is sufficiently unique among the siblings that no exclusion is necessary.

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