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 the result cap (default 50, max 100), the non-enumerable fallback shape (is_enumerable:false with balance), and the $0.002 price. It omits pagination/cursor behavior beyond the cap and any error or rate-limit behavior.

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 behavior, then cap, fallback, example, price, alternatives — a sensible order with no filler sentences. The pricing/related-link tail is dense but each clause carries routing or cost information an agent would otherwise lack.

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?

For a 6-parameter tool with no annotations and no output schema, the description covers the main call path and one fallback return field, which is meaningful. However, it does not describe the general return shape (array of token ids, balance field) or resolve the wallet/network aliases, so an agent still has gaps.

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 0%, so the description must compensate, and it only partly does: it clarifies contract, address, chain (via the example) and limit (default/max). It says nothing about the 'wallet' parameter versus 'address', or 'network' versus 'chain', leaving two ambiguous aliases undocumented.

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 ('List every ERC721 token_id a wallet owns in a collection') and even names the underlying mechanism (balanceOf + tokenOfOwnerByIndex). It is clearly distinguishable from the sibling chain_nft_owner, which resolves a single id.

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?

The 'Related' tail routes the agent explicitly: single-id owner lookup via /chain/nft-owner, metadata via /chain/nft-metadata, combined via /nft. That is real alternative-naming, though it never states an explicit when-not condition or prerequisite (e.g. that the collection must support ERC721Enumerable) as a usage rule.

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