reverse_geocode

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

No annotations provided, so description must disclose behavior. It mentions 'nearest place' and provides parameter ranges (lat, lon, zoom) but lacks details on rate limits, authentication, error handling, or response format beyond basic components.

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?

Well-structured with a clear summary followed by parameter and return descriptions. Slightly verbose due to docstring format (Args/Returns) but information is organized and front-loaded.

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?

No output schema, so description must explain returns. It briefly mentions 'Place name, address components, and bounding box' but lacks examples, error cases, or details on address structure. Adequate for basic use but incomplete for complex scenarios.

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 coverage is 0% but the description adds meaningful explanations for each parameter: lat/lon ranges, zoom levels, language examples, output_mode options. This compensates well beyond the schema.

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 the tool reverses geocode coordinates to a place name and address, specifying inputs (lat, lon) and outputs (display name, structured address, bounding box). Distinguishes from siblings like geocode (forward) and batch_geocode.

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 through parameter descriptions (zoom levels for detail, language for localization) but no explicit guidance on when to use this vs siblings like nearby_places or when not to use.

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