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

Annotations already declare readOnlyHint, destructiveHint false, idempotentHint true, and openWorldHint true. The description adds that results are sorted by distance with district info, but does not disclose additional behavioral traits like rate limits, pagination, or coordinate bounds beyond the implicit UK scope. With strong annotation coverage, the description adds moderate value.

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 two sentences, front-loaded with the primary action, and contains no filler. Every sentence adds value, making it highly concise.

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?

The tool has complete input schema, output schema present, and rich annotations. The description adds the use case (reverse geocoding) and data source (Postcodes.io). It is complete for a simple reverse geocoding tool, though it could mention behavior for out-of-UK coordinates. Given openWorldHint, this is acceptable.

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?

All three parameters (lat, lon, limit) have full descriptions in the input schema (100% coverage). The description adds no extra parameter-level meaning beyond the schema, so baseline of 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?

The description states the exact function: finding nearest UK postcodes to lat/lon coordinates, sorted by distance with district info. It clearly differentiates from siblings like lookup and validate by specifying 'reverse geocoding' and the data source.

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 explicitly says 'Use for reverse geocoding in the UK', which provides clear context. However, it does not explicitly state when not to use this tool or mention alternatives among the three sibling tools, though the purpose is sufficiently distinct.

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