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

With no annotations, the description carries the full burden and does well: it discloses the data universe (~1,000 top-PnL wallets plus 300 whales), the billing model ($0.01 USDC per call via x402 on Base), and the failure semantics (no trade seen = 404 and not charged). It stops short of stating rate limits, latency, or the response envelope, which matters somewhat given there is no output schema.

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?

Purpose is front-loaded in the opening clause, followed by scope, billing, and error behavior in descending order of importance. The first sentence is dense but every clause adds a distinct fact; only mild compression would improve it.

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 paid, unannotated, output-schema-less tool, the description supplies what an agent needs to decide and call: data contents, coverage universe, time window, cost, and 404 billing exemption. The remaining gap is the response shape and whether the returned wallet list is truncated or paginated.

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%, so both parameters are already documented, and the description largely restates them (1-72 h window). The one genuine addition is the implicit constraint that the mint must be a pump.fun/PumpSwap token, which narrows valid inputs beyond the schema's generic 'Solana token mint address'. That is useful but thin, so the baseline of 3 fits.

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 and verb chain: smart-money activity on one Solana token, covering which top-PnL wallets/whales bought or sold, net SOL flow, and accumulating/distributing signal. The enumerated output fields and the explicit 'pump.fun / PumpSwap mint' scope make it unmistakable against risk-oriented siblings like tokenrisk_check or tokenrisk_verdict.

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 through scope cues (1-72 h look-back, pump.fun/PumpSwap mints only) and the 404-on-no-trade note tells the agent what a null result means. However, it never names an alternative tool or states when NOT to use it, so the agent must infer that tokenrisk_verdict/verdict_lite are the risk-check counterparts rather than substitutes.

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