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

Annotations already mark it read-only, non-destructive, and closed-world; the description adds substantial behavior beyond that: no chain connection, no balance/nonce lookup, `isValid` does not guarantee settlement success, Solana payloads are refused explicitly, and settlement is omitted because broadcasting spends gas.

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 important constraints are front-loaded and the description is dense with useful context. The final feedback paragraph is less relevant to selecting or invoking the tool, keeping it short of perfect conciseness.

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?

Given no output schema, the description explains the response shape (`{isValid, invalidReason?, payer?, message}`) and the key limitation of `isValid`. With fully described input parameters and rich behavioral caveats, an agent has enough to call it 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?

Schema description coverage is 100%, so the three parameters are already documented. The description adds high-level meaning about EIP-712 signature recovery and scheme/network/recipient/amount/validity-window checks, but it does not add parameter-specific semantics beyond what the schema provides.

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 precise verb and resource: check an EVM `exact` x402 payment OFFLINE, and it names the return shape. It distinguishes the operation from settlement by saying `/settle` is deliberately not offered and explains that this is the tool form of `POST /verify`.

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 clear usage context: free, unauthenticated, offline verification of EVM `exact` payments, with explicit exclusions for on-chain balance/nonce checks, Solana payloads, and settlement. It does not name a sibling verification tool as an alternative, but the when/when-not boundaries are clear.

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