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

Annotations already cover read-only, idempotent and non-destructive status, but the description adds material behavior beyond them: best-effort semantics with an explicit failure mode, the caveat that a CEX origin is a signal not an identity, and the commercial terms ($0.10/call over x402 on Base, prepaid x-credit-token header for unlimited, no free tier). That is exactly the operational context annotations cannot convey.

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?

The core purpose and the sibling contrast are front-loaded, and the pricing/auth line at the end is genuinely useful. It is dense with em-dash clauses and a few rhetorical flourishes ('One verdict compliance can refuse on', 'Not financial advice') that could be trimmed, but no sentence is wholly wasted.

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?

Covers purpose, scope limits, hop semantics, cost/auth mechanics and reliability caveats for a tool that is read-only with an output schema and a fully documented two-parameter input. An agent has everything needed to select and invoke it correctly.

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% for both parameters, so the schema already documents 'wallet' and 'hops' (default 5, max 8). The description restates 'Required input: wallet' and 'up to 8 hops' without adding format or syntax 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?

States a specific verb and resource ('trace a wallet's money back to a CEX, a bridge, or a sanctioned address') and defines the output as classification of funding origin. It also explicitly differentiates itself from the sibling first_funder ('first-funder goes one hop; this walks the funding chain back up to 8 hops'), so an agent can route without opening either 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 the selecting condition (multi-hop provenance vs the one-hop first_funder) and the outcome framing ('one verdict compliance can refuse on'). It also states a boundary condition — internal-transfer funding is invisible and ends the walk — which tells the agent when the result will be incomplete rather than leaving that to be discovered empirically.

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