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

Annotations already cover read-only/no-destroy/open-world status, but the description adds real value beyond them: error contracts (404 missing contract, 422 non-ERC-721, both uncharged), pricing ($0.01/call via x402 or card key, first 25 free, failed calls free), and that repeats are billed — consistent with idempotentHint=false. It never states the response shape beyond name/symbol, and doesn't mention rate limits, which keeps it shy of a 5.

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 core operation and the sibling disambiguation, then error and billing facts. Dense but mostly earned; the pricing/charging sentences are the longest portion relative to the operation's simplicity, so not perfectly tight.

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 discloses what comes back (balance plus collection name and symbol), the two failure modes and their billing treatment, and the prerequisite that both arguments are 0x addresses. Nothing an agent needs to invoke it correctly is missing.

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%, so baseline is 3; the description still adds meaning by saying both inputs are 0x addresses and that the contract must be a valid ERC-721 collection (else 422), which ties the parameter to a failure mode. It adds no format examples or distinctions beyond that.

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 precise verb and resource: counts how many NFTs of one ERC-721 collection a wallet holds on Arbitrum One (balanceOf), plus returns collection name and symbol. Explicitly distinguishes itself from arb_nft_owner ('for who holds one token id use arb_nft_owner'), so an agent can pick between the two 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?

Names two concrete use cases (gate check before a token-gated action; verifying a wallet still holds a collection) and routes the alternative case (who holds a specific token id) to arb_nft_owner. Both when-to-use and when-not-to-use are present.

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