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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered and the description does not contradict it. It adds the REST route (GET /v1/geocode/reverse), which is useful orientation but says nothing about auth, rate limits, or whether multiple results are returned when limit > 1.

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 short sentences, front-loaded with the purpose and followed by the endpoint reference. Nothing is bloated, though the REST route line contributes only marginal value to an agent choosing the tool.

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 carries the burden of explaining what comes back, and it does not say what the response contains or how limit affects it. For a six-parameter geocoding call it is minimally adequate rather than complete.

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%, so every parameter (lat, lon, lang, type, limit, format) is already documented in the schema. The description adds no syntax, defaults, or format details beyond that, 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 second clause, 'turn coordinates into the nearest address / place,' gives a concrete verb and resource that makes the direction of the transformation unmistakable and implicitly separates it from the forward-geocoding siblings (geocode_search, geocode_autocomplete). It stops short of 5 because no sibling is named explicitly, so the agent must infer that separation.

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 statement of when to choose this over geocode_search, geocode_autocomplete, or place_details, and no prerequisites or exclusions. The only guidance is the implicit 'you have coordinates' framing, which is left to inference.

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