geocode_reverse

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

Mentions 'via Nominatim' but does not disclose rate limits, data source, or mutation behavior. No annotations provided, so the description carries full burden but adds minimal behavioral context.

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?

Single, well-structured sentence with verb first and no extraneous information.

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?

Adequate for a simple tool with output schema, but lacks details on error handling, performance, or usage constraints (e.g., coordinate bounds).

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 has 0% parameter descriptions. Description mentions coordinates (EPSG:4326), which clarifies that lat and lon are in decimal degrees, but does not specify valid ranges, order, or typical format.

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?

Clearly states it performs reverse geocoding of WGS84 coordinates to a street address via Nominatim. Distinguishes from sibling tools like geocode_nominatim (likely forward 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?

Implied usage for reverse geocoding, but no explicit guidance on when to use vs alternatives (e.g., forward geocoding tools) or any prerequisites.

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