reverse_geocode

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

No annotations are provided, so the description carries full burden. It implies a read-only lookup but does not explicitly state that the tool is non-destructive or detail any side effects, permissions, or rate limits. The behavioral traits are partially covered (e.g., zoom level impact), but more transparency would be beneficial.

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 efficiently structured with a brief intro, an Args section, and a Returns section. Every sentence adds value: it defines the operation, lists parameters with context, and summarizes output. There is no redundancy, and it is appropriately sized for a 5-parameter tool.

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?

Given the lack of an output schema, the description should detail the return structure. It mentions 'display name, structured address, and bounding box' but does not specify the format (e.g., JSON keys or text). For a tool with 5 parameters and no output schema, more detail on the return would improve completeness.

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 0%, so the description compensates by explaining each parameter: lat/lon ranges, zoom levels with examples, language format, and output_mode options. This adds meaningful context beyond the schema's type/default information. However, it lacks detailed examples for the language parameter.

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 purpose: 'Reverse geocode coordinates to a place name and address.' It specifies the input (coordinates) and output (display name, structured address, bounding box), making it unambiguous. The verb 'reverse geocode' is specific to the operation.

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 does not provide explicit guidance on when to use this tool versus alternatives like 'geocode' or 'nearby_places.' While the purpose implies it's for coordinate-to-place conversion, no when-to-use or when-not-to-use context is given, which would help the agent choose among siblings.

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