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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered; the description adds genuinely useful non-annotation context: the return shape (first funder, contract-vs-EOA, initial value, wallet age) and, critically, pricing/auth behavior ($0.04/call via x402, prepaid x-credit-token header, no free tier, no API key). These are exactly the extras that change how an agent invokes the tool.

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 lead question is a strong front-load, but the body pads with repeated statements ('wallet= required' then 'Required input: wallet'), a filler 'Not financial advice', and slightly breathless marketing framing. It is longer than the content requires.

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 an output schema present, return values need not be re-explained, yet the description still covers scope, output shape, and payment/auth requirements. Little an agent needs in order to call it correctly is missing; only explicit differentiation from sibling provenance tools is absent.

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 the single 'wallet' parameter, so the baseline is 3. The description only restates 'wallet= required' and adds no format, chain, or validation semantics beyond the schema.

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 ('Traces a Base wallet back to its EARLIEST transaction and resolves who first funded it') and enumerates the funder categories it distinguishes (exchange/bridge, anon EOA, contract). The 'sybil/origin screen no other Base tool gives' line helps separate it from the many sibling wallet-intel tools.

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?

Usage is implied via 'the counterparty check before you transact' and 'trace the cluster', giving the agent a sense of when it fits. However, it never names or contrasts a sibling (fund_trace, funding_radar, counterparty_check are all nearby) and gives no explicit when-not condition.

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