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

With no annotations, the description carries the full behavioral burden. It does disclose a genuinely useful non-schema trait — x402 pricing at $0.02/call in USDC on eip155:8453 — but says nothing about ordering (top by what), how 'limit' caps results, pagination, or failure behavior for an invalid contract/chain. Partial coverage only.

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 value proposition is front-loaded in the first clause, which is good, but the third sentence contains a grammatical break ('needs to who owns the collection') that makes the usage condition harder to parse than necessary. Three sentences for a three-parameter tool is reasonable length, but the middle sentence does not hold together cleanly.

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, so the description must describe returns — and it does, naming quantities, individual/cumulative percentages, and concentration statistics. The main remaining hole is ordering and limit semantics, but for a read-only distribution endpoint the 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 all three parameters (contract, chain, limit) are already documented, giving a baseline of 3. The description adds no extra meaning — no defaults, no maximum for 'limit', no format hint for the contract address (e.g. checksum/case) — so it neither compensates nor detracts.

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 and verb ('Top holders of any NFT collection') and enumerates exactly what is returned: quantities, individual and cumulative ownership percentages, concentration statistics. This clearly separates it from siblings like nft_collection_activity, nft_wallet_nfts, and crypto_wallet_snapshot without needing to open any 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?

Explicitly gives a use condition ('Use this when an agent needs to [know] who owns the collection, and how concentrated is it') and frames the downstream decision ('before valuing or recommending a collection'). No exclusions or named alternative tools are offered, so it stops 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.