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

Annotations already declare read-only, non-destructive, non-idempotent, open-world, and the description goes well beyond: contracts are excluded, plain wallet-to-wallet transfers only count in netAll, per-call billing with the first 25 free and failed calls free (which explains why repeats aren't free despite being a read), and default chain/blocks 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 question it answers, then scoping, then usage, then pricing. It is dense but nearly every clause carries information; 'reads or computes only and changes nothing' partly restates readOnlyHint, which is the only real redundancy.

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 supplies the returned fields (bought, sold, net, transfers) and the netAll nuance, plus cost and chain defaults. Nothing an agent needs to call this correctly and interpret the result 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 the baseline is 3; the description still adds interpretation by stating Base is the default chain and that the default 1800 blocks is roughly an hour on Base versus six hours on Ethereum, plus an address example. It doesn't clarify what limit means for ordering or whether netAll is a field versus a mode.

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?

Names a specific verb+resource: the wallets that bought or sold an ERC-20 from DEX pools/routers over recent blocks, with the chains covered and the metrics returned. It is clearly distinct from siblings like wallet_audit (single wallet) or token_report (token fundamentals), so an agent can route without opening schemas.

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 when-to-use rule: 'Use to see who accumulates or dumps a token before you trade it.' It does not explicitly name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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