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

Beyond the readOnly/openWorld annotations, the description discloses the result depth (newest 50 transfers only), the exact heuristic behind the wash flag (A→B→A round trips), data gaps (no prices/royalties), and the payment model ($0.002 USDC via x402, failed calls free). These are material behavioral facts an agent cannot get from structured fields.

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 tight sentences: scope and returns first, then the wash heuristic, then the data-absence caveat and cost. No filler, and the most decision-relevant facts (what you get, what you don't, what it costs) are front-loaded.

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?

An output schema exists, so return-value explanation is unnecessary; the description instead covers the things structure can't — coverage depth (50 transfers), the detection heuristic, the missing price data, and the x402 billing terms. Nothing an agent needs to call this correctly or decide against it 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% and the single 'address' parameter is already documented as a 0x + 40 hex ERC-721 contract address. The description reinforces that this must be an Ethereum ERC-721 contract, but adds no format or validation detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific resource (ERC-721 collection activity on Ethereum via Blockscout) and enumerates exactly what is returned — name, holder count, supply, and the newest 50 transfers — plus the wash-signal flagging. That is enough to distinguish it from generic siblings like crypto_honeypot_detector or crypto_whale_alert_transfers 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?

It implies usage by stating what the source does and does not provide ('No sale prices, floor price or royalties'), which tells an agent when this tool is the wrong choice for pricing questions. However, it never names an alternative tool or explicitly says 'use X instead when you need floor price,' so the routing guidance is implied rather than stated.

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