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

Annotations already declare readOnly/idempotent/openWorld and non-destructive, covering the safety profile. The description adds that the return value is a formatted address, which is genuinely useful given no output schema, but says nothing about accuracy bounds, rate limits, or edge-case behavior.

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?

Three short sentences, purpose and return value front-loaded, with a concrete example at the end. No wasted padding, though the example largely duplicates the schema's examples block.

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 simple three-parameter lookup with full schema coverage and no output schema, the description states the input intent and the return shape (formatted address). Only error/edge behavior and any formatting options are absent, which is minor here.

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 100% with descriptions and an examples array covering all three parameters, so the schema does the heavy lifting. The description's inline example repeats the same lat/lon values rather than adding new semantic detail, so baseline 3 is appropriate.

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?

Specific verb+resource: 'Reverse geocode coordinates to an address'. The word 'reverse' implicitly separates it from the sibling radar_geocode, but it never names that sibling or any other Radar tool, so the differentiation is inferred rather than explicit.

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?

Usage is implied by the operation name – use this when you have lat/lng and want an address – but there is no explicit when-to-use, when-not-to-use, or pointer to radar_geocode for the opposite direction.

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