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

Annotations already cover the read-only/open-world/safe profile, so the bar is lower. The description adds real behavioral context beyond them: results may come from cache or a fresh lookup, include a confidence value, and failures are reported as not-found rather than a guessed coordinate.

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?

Two tight sentences with no waste; the batch limit and return shape are front-loaded, and the not-found guarantee closes efficiently.

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?

With no output schema, the description usefully sketches the return shape (lat, lng, confidence, cache vs fresh, explicit not-found). For a single-parameter tool this is nearly complete, only lacking format/precision or input-normalization specifics.

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% and the only parameter is documented there as '1–10 addresses', so the schema does the heavy lifting. The description's 'up to 10 addresses' is consistent but adds no syntax or format detail beyond the schema.

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 states a specific transformation: addresses in, coordinates (lat/lng) out, with a 10-address batch cap. It's clearly a forward geocoder, implicitly distinguishing it from the reverse_geocode sibling, but it never names that sibling explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as reverse_geocode. The 10-address cap implies a batching use case but the agent gets no routing help for choosing among the many location-related siblings.

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