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

Beyond the readOnly/openWorld annotations it discloses cost model ($0.01/call via x402 or card key, first 25 free, failed calls free), the non-idempotent charge-on-repeat behavior, that results are limited to a recent-block window rather than full history, and that native transfers are excluded. These are material facts an agent cannot get from the annotations or schema.

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 resource and output shape, then scope limits, then use cases, then pricing. Dense but every clause is informative; the pricing sentence is the longest and could be tightened, and the example address is somewhat expendable.

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 compensates by enumerating returned fields (ranked counterparties, sent/received counts, tokens, USDC in/out, first/last block, wallet vs contract). Minor gaps remain on result-size limits or how many counterparties are returned and in what order beyond 'ranked by transfers'.

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%, including chain defaults and block-time guidance, so the schema already carries parameter meaning. The description adds only a concrete address example and the scan-window framing; it does not explain how the blocks parameter trades off runtime versus result completeness beyond what the schema says.

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+resource (related wallets of a 0x address), the exact data source (Transfer logs, ERC-20 only), the ranking criterion (by transfers), and the output dimensions. An agent can tell it apart from *_token_transfers or wallet_transactions without opening any 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 three concrete when-to-use scenarios (map trading counterparts, vet linked wallets before paying, trace fund flow) and an explicit exclusion (native-coin transfers not included). It does not name a sibling to use instead when the exclusion applies, e.g. a transaction-level tool for native transfers, so routing is only implied.

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