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

Despite annotations covering readOnly=false and idempotent=false, the description adds critical context absent from annotations: the tool is paid per call (0.10 USDC on Base via x402), requires a two-step payment handshake, and only charges if the check succeeds and settlement occurs. This is exactly the kind of operational detail an agent needs before invoking.

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 description is front-loaded with the core purpose and usage, then flows into payment mechanics. It is dense but every sentence serves a purpose; minor length is justified by the non-trivial x402 payment handshake.

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 still explains what the tool returns (whether the USDC moved) and how payment terms and settlement are surfaced via _meta. It covers the full paid-call workflow, including the failure/no-charge behavior, which is essential given the tool's open-world and paid nature.

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%, so the schema already documents every parameter including patterns and semantics. The description summarizes the expected fields ('recipient, sender, minimum amount and confirmations') but does not add meaning beyond what the schema provides, which matches the baseline of 3 when schema coverage is high.

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 states a specific verb and resource ('Reads a Base transaction and says whether it paid the USDC claimed') and enumerates the verification dimensions (to, from, amount, confirmations). It is clearly distinguishable from siblings like check_x402_endpoint or chain_status because it focuses on validating a specific USDC payment on Base.

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 gives a clear triggering condition: 'Use it when someone says they paid you, before you deliver.' It also names optional expectations an agent can supply. It does not explicitly state when not to use it or name an alternative for failed checks, but the context is strong enough for correct selection.

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