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

Annotations already cover read-only, open-world, idempotent, and non-destructive traits, so the bar is lower; the description nonetheless adds credit-worthy behavior: a per-address cost of $0.001, guaranteed input-order results, and per-item found=true/false signaling partial success. It doesn't mention rate limits or whether billing occurs on failed lookups.

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?

Three short sentences, front-loaded with the action and the limit, then result semantics, then cost. Nothing is redundant and every sentence carries operational information.

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 single-parameter read tool with no output schema, the description covers ordering, partial-failure signaling, and pricing—enough to invoke it correctly and anticipate billing. The shape of the actual coordinate payload is left unstated, a minor gap given no output schema exists.

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?

There is only one parameter and schema coverage is 100%, with minLength/maxLength and maxItems already documented in the schema. The description restates the 50-item cap but adds no new detail such as address format expectations or how invalid entries are handled.

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 (geocode), resource (addresses), and batch scope ('up to 50 addresses in one call'), which inherently distinguishes it from the single-address 'geocode' sibling. It does not explicitly name alternatives, so differentiation is implicit rather than stated.

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 phrase 'up to 50 addresses in one call' implies this is the multi-address path, but there is no explicit 'use this instead of geocode when...' guidance and no mention of when to prefer batch_reverse_geocode. Usage is inferable from scope alone.

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