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

Annotations declare readOnlyHint and openWorldHint, but the description adds substantial behavioral context: free-call quota, per-call price, in-band x402 payment parameter, caching, provider, and ODbL attribution. This goes well beyond the structured annotations.

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 compact and mostly front-loaded, but it leads with service-wide pricing before stating the tool's purpose and repeats the 'up to 5' limit in both the purpose and usage sentences. Minor redundancy keeps it below top marks.

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?

For a paid batch geocoding tool with full schema coverage and an output schema, the description covers the essential calling context: quota, pricing, payment mechanism, batch limit, provider, cache, and attribution. It stops short of explaining partial-failure behavior or error cases.

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 coverage is 100%, so the schema already documents the separator, max count, and optional ISO-2 country filter. The description adds that place names are accepted in addition to addresses, but otherwise mostly restates schema semantics; this is the baseline for high-coverage schemas.

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?

States a specific verb and resource ('Geocode batch'), the batch size ('up to 5'), the outputs ('coordinates and a structured address'), and the optional country filter. The batch scope clearly distinguishes it from the single-address sibling 'geocode'.

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 explicitly says when to use it: 'Use geocode-batch for up to 5 addresses at once.' However, it does not explicitly name the sibling 'geocode' as the alternative for single-address requests or state when not to use this batch tool.

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