Reverse geocode GPS coordinates

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

Annotations already cover the read-only and non-destructive nature. The description adds the configured geocoder behavior and the Nominatim default, which is valuable. However, it does not mention output format, possible failures, or external service dependencies beyond the env var, so it is not rich enough for a higher score.

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?

One sentence, front-loaded with the action and outcome, then a brief config note. No wasted words.

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 simple read-only reverse-geocoding tool, the description covers the core outcome (address) and the default provider. The schema fully documents parameters and annotations cover safety. Missing details like exact return structure or error behavior are not critical for this use case, though a slightly richer description would be more 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%, with each parameter already documented. The description adds no further parameter-level semantics beyond noting that the input is GPS coordinates, so the baseline score of 3 is appropriate.

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 uses a specific verb ('converts') and clearly identifies the resource ('GPS coordinates' to 'address'). It also differentiates from sibling tools, which focus on stats, tracks, and timelines, not geocoding.

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 gives useful configuration context (defaults to OpenStreetMap Nominatim, overridable via DAWARICH_GEOCODER_URL) and clearly implies when this tool should be used. It does not explicitly state when not to use it or name alternatives, but no comparable sibling geocoder exists.

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