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

Annotations only declare readOnly and openWorld; the description adds substantial context beyond that: a fixed-denomination pool model, an explicit caveat that the anonymity set is an approximation valid 'if nothing else moved the balance', and a full pricing/billing model (x402 on Base/Solana/Arc, $0.002 per successful call, failures free). The note that this is sanctioned-protocol public on-chain state also sets expectations about the data's nature.

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?

A single dense paragraph, front-loaded with what is returned and followed by scope limits, caveats, and price. Every clause carries information, though the pricing sentence is long and could be split for readability.

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 shapes needn't be explained; the description instead covers the non-obvious parts (approximation semantics, chain restriction, cost). Only data freshness or update cadence is left unaddressed, which is minor for a read-only pool-state tool.

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?

With zero parameters, the baseline is 4; there is nothing to mis-specify. The description adds a little by implying the denomination tiers are fixed and returned as a set rather than selectable, which prevents an agent from hunting for a denomination argument.

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 resource (Tornado Cash ETH pools at 0.1/1/10/100 ETH denominations) and the exact data returned: pool balance, contract code presence, and an approximate anonymity set. It is distinguishable from siblings like crypto_sanctioned_crypto_wallets because it is pool-state specific. It lacks an action verb, so the operation is implied by the noun phrase rather than stated.

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 description gives negative scope ('Ethereum pools only; no relayer or multi-chain data'), which steers an agent away from expecting relayer or cross-chain metrics. However, it never says when to choose this over a neighboring tool or what question it answers, so usage must be inferred from the noun list.

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