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

With no annotations the description carries the full behavioral burden, and it does disclose the paid nature of the call ($0.02/call in USDC on eip155:8453) and the sort order, which are genuinely useful. It does not say whether the call is read-only, how 'limit' interacts with large wallets, or what an empty/EOA wallet returns, leaving real gaps for a no-annotation tool.

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 short sentences, front-loaded with the result shape and followed by the pairing and pricing facts; no padding. It loses a point for the garbled clause 'needs to every NFT collection' and for burying the price in the same breath as the usage clause.

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?

Despite having no annotations and no output schema, the description compensates by describing the return shape (collections plus quantities, sorted by size) and the payment requirement. Only edge behavior (pagination/truncation via limit, empty wallets) is left unstated, which is a minor gap for a 3-parameter tool.

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% (address, chain enum, limit all documented inline), so the baseline is 3. The description adds no extra meaning to these parameters — it never explains ordering versus limit or what 'Max collections' truncation implies.

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 ('look up an address's NFT portfolio across collections') plus the exact scope of the result ('each collection held, quantity owned, sorted by size'), which separates it from siblings like nft_collection_activity or nft_holder_distribution. It also names crypto_wallet_snapshot as the complementary tool, so an agent can place it without opening a 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 triggering condition ('Use this when an agent needs to [see] every NFT collection a wallet holds, in one call') and positions it as the enrichment endpoint that pairs with wallet-snapshot. There is no explicit when-not clause or named alternative for the portfolio-of-one-collection case, 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.