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 that the call is paid ($0.001 per call), the accepted payment tokens (USDC on Arc/Base/Solana or XNT on X1), and the x402 two-phase handshake needed before a purchase completes. It does not state failure behavior for an invalid token/chain or any rate limits, so it is strong but not exhaustive.

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, zero filler. The chain coverage and returned fields are front-loaded ahead of the payment mechanics, so the agent gets the core capability before the operational detail.

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?

There is no output schema, and the description compensates by naming the returned fields (name, symbol, decimals, total supply) and explaining the payment flow and cost. It leaves error/edge-case behavior unstated, but for a metadata read tool this is nearly complete.

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 baseline is 3. The description adds genuine meaning beyond that by explaining `payment` as part of a two-call negotiation ('call once without `payment` for the terms, sign them... call again with `payment`'), which clarifies the non-obvious control flow around that parameter.

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 and resource (token info + total supply) and enumerates exactly what is returned: name, symbol, decimals, total supply. This cleanly separates it from siblings like evm_token_balance (a wallet's balance) and crypto_price (market pricing), so an agent can route without opening the schema.

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 a clear operational sequence: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. That is actionable context most tools lack. It stops short of naming alternatives or stating when not to use this tool (e.g., versus evm_token_balance).

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