reverse_geocode

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It details the output components (formatted address, administrative hierarchy, OSM metadata, etc.) and specifies the coordinate system (WGS84). It does not cover error handling or edge cases, but for a read-only conversion tool, the disclosed behavior is adequate and informative.

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?

The description is well-structured with a clear one-sentence summary, a brief explanatory paragraph, and labeled Args/Returns sections. It front-loads the purpose and then provides necessary details. The Returns list is somewhat verbose, but each item adds functional value and the overall length is proportionate to the tool's complexity.

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 two-parameter geocoding tool with no output schema and no annotations, the description is quite complete. It covers purpose, usage context, parameter semantics, and return value structure. Missing aspects like potential failure modes (e.g., invalid coordinates, offline usage) are minor given the simplicity of the operation.

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?

The input schema provides only type and requirement, with no parameter descriptions (0% coverage). The description compensates by explicitly defining both parameters with format details ('decimal degrees, WGS84'), adding semantic meaning beyond the raw schema. It lacks constraints like valid ranges, but the essential format information is present.

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 clearly states a specific verb ('Convert') and resource ('geographic coordinates to a detailed address and location description'). The opening sentence directly mirrors the tool name, and the phrase 'Useful for translating GPS coordinates into human-readable locations' reinforces the reverse geocoding use case, distinguishing it from forward geocoding (geocode_address) and other siblings.

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 provides a clear use case: translating GPS coordinates into human-readable locations. It does not explicitly name alternatives or when-not-to-use scenarios, but the tool's purpose is unambiguous and the sibling context implies when it should be chosen over geocode_address.

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