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

With no annotations, the description carries the full burden and does disclose the material traits: cost ($0.001 per call), payment rails accepted (x402 USDC on Arc/Base/Solana or XNT on X1), and the auth/terms workflow. It omits any note on rate limits, error handling, or how pending vs confirmed nonces are derived, which keeps it from a 5.

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, front-loaded with what the tool returns and followed by cost and payment mechanics. Dense but each clause earns its place; the pricing sentence could arguably be trimmed but is operationally relevant.

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?

For a 3-param read tool with no output schema and no annotations, the description covers purpose, returned values, pricing, and the payment handshake, which is enough to invoke it correctly. Minor gaps remain around default chain confirmation and repeated-call cost implications.

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 coverage is 100%, so the baseline is 3; however, the description adds real meaning around the `payment` parameter by explaining the call-once-then-sign-then-call-again sequence, which the schema's terse PAYMENT-SIGNATURE note does not convey. Chain and address semantics are left to the schema.

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 specific resource (wallet nonce), enumerates the supported chains, and unpacks what it returns (confirmed count, next nonce, pending transactions). The resource is distinct enough from siblings like evm_balances_bulk or evm_allowance that an agent can route correctly, but no sibling is named, so it stops short of a 5.

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?

Gives clear procedural context for the two-step x402 flow: call once without `payment` for terms, sign, call again with `payment`. It does not state when to prefer this over a sibling such as evm_tx or how it relates to nonce fields there, so there are no explicit alternatives or exclusions.

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