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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: a free daily allowance with a $0.002 USDC per-call x402 charge beyond it, which matters for an agent deciding whether to loop calls.

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?

Two sentences, no padding, with the core operation front-loaded and the commercial condition second. Every clause carries 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?

An output schema exists, so return values need not be explained. Still missing for a geospatial tool: search radius or coverage assumptions, ordering/limit behavior, and any accuracy caveats, which leaves the definition adequate but not complete.

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 100%, so lat, lon and limit are already documented in the schema; the description only restates that the operation is coordinate-based. No extra semantics (e.g. coordinate ordering, limit ceiling, search radius) are added.

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?

States a specific operation (nearest postcodes) over a specific input (latitude/longitude), which is a clear verb+resource pairing. It does not, however, distinguish itself from the sibling uk-postcodes__nearest, which an agent could reasonably confuse with a reverse-geocode call.

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 gives no when-to-use guidance or named alternatives; a reader must infer that this is the tool for coordinate input rather than a postcode input. The pricing sentence is cost information, not usage direction.

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