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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint true), so the description's job is to add context – and it does, disclosing the per-call cost and payment rail ($0.001, USDC on Base via x402), which an agent needs before invoking. It also discloses the internal rule that canonical tokens are flagged in Transfer decoding. It does not mention failure handling for malformed hashes or latency/rate 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?

Two sentences, no filler, with the return payload enumerated compactly. Minor structural weakness: the cost/payment rail is placed ahead of the purpose, so the agent reads pricing before learning what the tool does.

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?

There is no output schema, and the description compensates by enumerating the returned fields and the possible transaction states in enough detail to interpret a response. Combined with annotations covering the safety profile and the description covering cost, an agent has what it needs to call this correctly.

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?

There is a single parameter whose schema description is fully covered ("Base tx hash", with a 0x+p64 regex). The description adds no format or syntax detail beyond the schema, so the baseline of 3 applies.

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 names the resource (a Base transaction) and enumerates exactly what it reports: state (not_found/pending/success/reverted), block, confirmations, from/to, fee in ETH, method selector, and decoded ERC-20 Transfer events. That is far more specific than a tautology. It stops short of naming the sibling it differs from (e.g. usdc_payment_check or x402_preflight), so an agent must infer the boundary itself.

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?

"Use to confirm a payment, swap or call landed" gives clear positive guidance on when to reach for this tool. There is no explicit when-not guidance or named alternative, so it lands at 4 rather than 5.

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