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

Beyond the annotations (readOnlyHint, openWorldHint), it discloses cost ($0.01 USDC on Base), that ambiguous matches fail without charge, what a successful response contains (signed observation, OFAC flags, confirmations, printable HTML), and a detailed x402 payment-continuation protocol. The payment boilerplate is somewhat generic and the price is stated twice, which keeps it from a 5, but the safety-relevant context (never send a separate transfer, never paste keys, inspect unknown-outcome authorizations) is genuinely valuable.

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?

The useful content is front-loaded, but the text is bloated: the price appears twice ('Price $0.01 USDC on Base... Price: 0.01 USDC'), and the illustrative-output disclaimer is restated two sentences apart. The long payment-procedure block, while relevant, crowds out the input contract.

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, but the description compensates with an illustrative response shape and a list of returned artifacts, and it explains the payment handshake an agent must follow. With six optional parameters and a novel pricing model, the definition is nearly sufficient to invoke correctly; only the parameter-level edge cases and effective timeout/retry behavior remain thin.

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 carry the load, and it does: log_index is framed as a disambiguator for tx_hash, amount is required to be exact decimal, and start/end must be past and span at most 90 days — constraints absent from the schema. It does not describe log_index bounds or the amount precision limit of 6 decimals that the schema encodes.

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 a specific verb and resource ('Verify a native Base USDC transfer') and enumerates the two accepted lookup modes. It also bounds scope negatively ('Not invoice ownership or finality proof'), which helps an agent avoid over-reading results, though it never positions itself against the sibling tools.

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?

It states the two concrete input paths (tx_hash with optional log_index, or pay_to + amount + start/end within 90 days) and the failure condition ('Ambiguous matches fail without charge'). It also states there is no free trial and that a non-x402 MCP client cannot complete a paid call, which is clear when-to-use context. It stops short of naming an alternative tool for cases this one declines.

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