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

Annotations already flag non-read-only, open-world, and destructive behavior, and the description adds genuine extra context: two-RPC receipt agreement, safe finality requirement, credit cost, and a refund policy for RPC failures. These are valuable traits not derivable from the structured fields, though it does not reconcile why a verification tool carries destructiveHint=true.

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 the core purpose, then layers in the amount format, finality/RPC mechanics, and billing. Five tight sentences; every line carries information, though the billing/refund detail could be tightened.

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 an output schema present, return values need no explanation, and the description covers the matching criteria, cost, and failure-refund behavior adequately. The main gap is the absence of explicit routing guidance against the sibling verification/inspection tools.

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 0%, so the description must compensate, and it only clarifies expectedAmountAtomic (decimal atomic string, 6 decimals). txHash, expectedPayer, and expectedReceiver are left to their expressive names and regex patterns, adding partial but not complete semantic coverage.

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 precise verb+resource: verify a Base transaction contains an exact native Circle USDC Transfer from expected payer to receiver for the exact atomic amount. It is unambiguous about the chain, token standard, and matching criteria, and clearly distinct from siblings like decode_usdc_transfers and get_transaction_status.

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 explains what verification entails (two-RPC receipt agreement, safe finality) and its cost, giving implied usage context, but it never says when to reach for this tool over decode_usdc_transfers or get_transaction_status. No explicit alternatives or exclusions are named.

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