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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses the paid model with a concrete price ($0.001 per call), the accepted payment rails, and that settlement happens inside the second call. It does not address whether repeated calls with the same `payment` payload would double-charge, which matters given idempotentHint=true, but the payment workflow itself is unusually well explained.

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?

Three tight sentences, front-loaded with what the tool returns and followed by pricing and the call protocol. Nothing is filler, though the parenthetical payment-rails list is dense and slightly interrupts the flow of the call instructions.

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 compensates by naming the returned fields, and it fully covers the non-obvious part of the tool — the x402 payment handshake. An agent has enough to make a correct first call and a correct paid second call without further exploration.

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 already 100%, so the baseline is 3; the description earns an extra point by explaining the temporal role of `payment` — the parameter is absent on the first call and present on the second — which the schema alone presents only as a static string field.

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 resource (ERC721 NFT) and enumerates the returned fields (owner, collection name and symbol, tokenURI), plus the supported chains. It is implicitly separable from evm_token_info, but it never names the sibling or states the ERC20-vs-ERC721 boundary explicitly, so it falls just short of 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?

The two-step usage is spelled out concretely: call once without `payment` to get terms, sign with your own wallet, call again with `payment` to complete the purchase. What is missing is guidance on alternatives (e.g. evm_token_info for fungible tokens) and prerequisites such as wallet/funding setup for USDC on Arc/Base/Solana or XNT on X1.

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