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

Annotations already declare readOnly=true, destructive=false, idempotent=false, so the safety profile is known; the description nonetheless adds real behavior: 404 on missing contract, 422 on nonexistent token, both uncharged, plus the charging model and that repeat calls are not free. The only minor gap is it does not state the response shape beyond the fields named, which is largely implied.

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 definition and alternatives, then errors, example, and pricing — a sensible ordering with no filler. The pricing information is stated twice in effect ('Price $0.01/call… first 25 free' and 'each call is charged, so repeats are not free'), a small redundancy in an otherwise dense paragraph.

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, yet the description still tells the agent what comes back (owner address, collection name, symbol), how failures behave, what it costs, and that it mutates nothing. For a two-parameter read tool that is everything needed 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 coverage is 100%, so the baseline is 3, but the description adds a worked example (contract=0x655C..., tokenId=1) that shows the expected address/id formats, and ties the two parameters to distinct failure modes (missing contract vs nonexistent token). That is meaningful meaning beyond the schema's one-line field notes.

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 — 'the wallet that holds one ERC-721 token id right now (ownerOf)' — and explicitly delimits scope to a single token on Avalanche, plus names the collection name/symbol as extra return data. It is unmistakably distinct from avax_nft_balance (counts) and avax_nft_metadata (token metadata).

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 concrete use case ('verify who holds an NFT before a trade, a mint gate or an airdrop') and routes to two named alternatives with their selecting conditions ('for how many a wallet holds use avax_nft_balance, for the token's metadata avax_nft_metadata'). Both when-to-use and when-to-use-something-else are covered.

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