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

With no annotations, the description carries the full burden and does well: it discloses the exact cost ($0.001 per call), the accepted payment assets and chains (USDC on Arc/Base/Solana, XNT on X1), and that signing happens in the caller's own wallet. It omits failure/refund behavior on an unsigned or underpaid call.

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?

Front-loaded with the return payload, then the pricing/payment mechanics in two compact sentences. No filler, though the parenthetical payment-asset list makes the middle sentence dense.

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?

No output schema exists, and the description compensates by enumerating the returned fields. Combined with zero annotations and full payment semantics, an agent has nearly everything needed; only error/payment-failure handling is unaddressed.

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% (baseline 3), but the description adds real meaning beyond it: the two-step payment handshake explains *how* the unusual `payment` parameter is meant to be used relative to a paymentless call, and it confirms the multi-chain `chain` options.

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 verb+resource: returns owner and metadata for an ERC721 token, enumerating the exact return fields (owner, collection name, symbol, tokenURI). The ERC721/NFT scope cleanly separates it from the fungible-focused sibling evm_token_info.

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?

Explicitly prescribes the call sequence: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. That is strong operational guidance. It never names an alternative tool or a when-not-to-use condition, so it falls short of a 5.

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