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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely non-schema context: results come back in input order and the call costs $0.001 per point, which matters for batching decisions. It omits what happens to points that fail to resolve and offers no rate-limit detail.

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?

A single tight sentence carrying the core action, the batch limit, the ordering guarantee and the price, with the verb and resource front-loaded. Nothing is wasted or padded.

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 one-parameter read-only lookup with rich annotations and a fully covered schema, the description supplies the operational facts an agent needs: batch ceiling, ordering and cost. Minor gaps remain around partial-failure behavior and output shape, though no output schema exists to defer to.

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%: the single points array with nested latitude/longitude bounds and WGS84 notes is fully documented in the schema. The description only contributes the input-order guarantee and repeats the 50-item cap already encoded as maxItems, so the baseline 3 applies.

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 gives a specific verb and resource ('Find the street addresses') plus the batch scope ('up to 50 latitude/longitude points in one call'), which implicitly separates it from a single-point reverse_geocode and a forward batch_geocode. It stops short of naming a sibling to route away from, so it is clear but not maximally differentiating.

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?

Usage is only implied: the 50-point cap and per-point pricing hint that small lookups may belong elsewhere, but the description never says when to prefer reverse_geocode or batch_geocode, nor any prerequisite for obtaining coordinates. The agent must infer the selection rule from the batch framing alone.

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