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

Annotations already declare readOnly/idempotent, so the description's added value is cost and data provenance: $0.002 per call with 10 free/day and an x402 payment-required result, plus that errors return isError and are not charged, and the underlying 10-day block-0 registry window. Missing rate limits or latency expectations, but the pricing and error-charging semantics are genuinely useful context beyond annotations.

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 and the kind taxonomy are front-loaded well, and the pricing/error sentences earn their place. There is some redundancy: 'Use it on wallets bundle_forensics lists' is repeated almost verbatim later in 'When to use: To check one wallet from bundle_forensics'.

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 values need not be explained, yet the description still defines the four classification labels and their thresholds, which is key interpretation context. Data source, cost model, error behavior, and routing to alternatives are all covered.

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% and both parameters (wallet base58 address, limit 1-100 default 25) are fully documented in the schema. The description adds no additional parameter guidance such as what limit controls in the result set, 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?

Opens with a specific question about a specific resource ('Is this Solana wallet a bundler?') and then enumerates exactly what the profile contains: block-0 buys over 10 days, creators bundled for, and bot-vs-dev-wallet classification. This is clearly distinguishable from sibling bundle_forensics (which lists wallets) and creator_launches.

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?

Explicitly says to use it on wallets returned by bundle_forensics or any wallet about to be copied, and names the alternative pump_wallet for trading performance, including that it lives on a different server. Both when-to-use and when-to-use-something-else are stated.

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