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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious behavioral context: the call is metered at 0.010 USDC and settles on Base & Solana Mainnet, which an agent needs to know before invoking a paid endpoint. It stops short of failure modes or rate-limit behavior.

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?

Two sentences, both load-bearing: the first carries the analytic scope and segmentation, the second the cost and chain coverage. No filler and the core capability is front-loaded.

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-shape explanation is not required, and the description plus annotations give an agent everything needed to call it correctly. Minor gap: no note on unsupported addresses or latency for a paid analytics call.

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?

Only one parameter and schema coverage is 100%, so the schema already explains the 0x/SPL address format. The description reinforces the dual-chain scope (Solana or Base) but adds no format or validation detail beyond the schema — 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+resource (who bought/sold a token) with concrete scope: last 24h, segmented into Smart Money, Whales, Fresh Wallets and Dev Clusters. That distinguishes it in substance from sibling tools like rugshield_tgm_holders or rugshield_smart_money_dex_trades, though it never names them explicitly.

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?

The intended usage (inspect buy/sell flow composition for a token) is implied by the description, but there is no explicit when-to-use, when-not, or routing to alternatives such as tgm_holders or smart_money_netflow.

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