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

Annotations convey almost nothing useful here (readOnlyHint false, openWorldHint true), so the description carries the load and does: it discloses pricing per call, the exact x402 payment handshake (call without payment to receive PaymentRequired, retry with _meta['x402/payment']), and the interpolation flag on returned coordinates. That is materially more than the annotations provide.

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?

Front-loaded with purpose and price, then scope caveat, then payment mechanics — a sensible order with no filler. It is dense, and the payment/HTTP-equivalent tail is long, but every clause carries operational 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?

With no output schema, the description must carry the return semantics, and it does partially (range_match/no_match, preserved house-number range, interpolated:true coordinates). The full response shape and error behavior are still unspecified, which for a paid call is a minor gap.

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% and the single nested address object documents every component, so baseline is met. The description adds only that address.state is required, which is already in the schema's required list, so there is little value beyond the structured field.

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 verb+resource (US address-validation leg via Census Geocoder) and pins the scope to the United States, which is what separates it from address_leg_nl and address_bundle. It also names the exact return vocabulary (range_match / no_match) so the agent knows what it is buying.

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?

Gives clear operating context: a free preflight endpoint to call first, and the interpretive caveat that a range match is not an existence verdict. It stops short of naming the sibling to use for a true existence verdict (address_verify), so the agent must infer the alternative.

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