geocode.reverse

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

No annotations are provided, so the description must disclose behavioral traits, but it only states the function. It omits details about synchronous/asynchronous behavior, authentication, rate limits, coordinate limits, or output format. Very little transparency.

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 single sentence is concise but lacks structure. It could benefit from separating purpose, parameters, and output, while remaining brief. Currently it is under-specified.

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?

Without an output schema, the description should explain the return value (e.g., formatted address, components). It does not cover common use cases, error handling, or limitations, leaving the tool's behavior incomplete.

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 has 0% description coverage and the description adds minimal meaning beyond 'coordinate'. It does not specify expected units (e.g., decimal degrees) or valid ranges for lat/lon, failing to compensate for the lack of schema descriptions.

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 the tool's function: reverse geocode a coordinate to a labeled address. It implicitly distinguishes from forward geocoding (geocode.address) and other geo tools, but lacks explicit differentiation from siblings like geo.nearby.

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?

No guidance on when to use this tool vs alternatives. Does not mention scenarios, prerequisites, or exclusions. The description only provides the basic purpose without context for appropriate use.

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