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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely useful non-schema behavior: a $0.05 USDC-on-Base cost, plan-key inclusion, and the fact that the archive is recorded live and cannot be rebuilt retroactively (a data-freshness caveat).

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 behavior in the first clause, then supporting detail. Minor redundancy in restating the $0.05 cost twice ('Costs $0.05 USDC on Base' then 'paid $0.05'), but otherwise tight and well ordered.

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?

For a single-param read tool with no output schema, the description adequately covers what comes back (balances, identity, insider/deployer records), the payment requirement, and a data-retention caveat. Only the explicit distinction from sibling wallet tools 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?

With a single required parameter at 100% schema coverage, the schema already documents 'address (Wallet address 0x…)'. The description adds no format, validation, or chaining detail beyond confirming the subject is a wallet, 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?

The description gives a clear verb+resource ('Follow a wallet across the accumulated holder-snapshot archive') and enumerates the returned payload (per-token balance then/now, ENS/Farcaster identity, insider/deployer records). It is distinguishable from generic detection siblings, though it never explicitly contrasts itself with closely named tools like robinx_wallet, robinx_identify, or robinx_wallet_receipt.

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?

It implies the use case (tracing a wallet's appearances across the snapshot archive) but offers no explicit when-to-use/when-not guidance and no named alternatives among the many sibling tools. The reader must infer this is the right pick over robinx_wallet or robinx_identify.

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