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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description goes beyond them with a concrete, decision-relevant fact: $0.004 USDC per call via x402, i.e. a paid micropayment operation. It also discloses the granularity of the confidence signal (building/street/city) and that alternatives are returned. It stops short of explaining payment/auth prerequisites or failure modes.

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?

A single dense sentence that front-loads purpose then lists outputs, ending with the cost caveat. Efficient, though the output enumeration makes it slightly list-heavy at the expense of input guidance.

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 correctly carries the return-value burden and does so thoroughly (parsed components, confidence levels, verdict, coordinates, timezone, alternatives). The gaps are on the input/usage side, not the output side.

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 only 50% ('address' has no description), so the description must compensate — but it is written entirely around return values and says nothing about the input. The 'country' restriction behavior is left to the schema alone.

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 ('Address verification and standardization') and enumerates the exact outputs it produces, so an agent knows precisely what comes back. However, it never distinguishes itself from the obvious sibling 'address_validate' (nor 'geocode'/'postal'), leaving overlap unaddressed.

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?

There is no statement of when to reach for this tool versus address_validate, geocode, postal or zip. The only context offered is the price, not usage conditions or exclusions.

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