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

Annotations already declare read-only, non-destructive, open-world behavior, so the description's main added value is the explicit 0.010 USDC cost on Base and Solana Mainnet — real, non-obvious behavior an agent must budget for. It does not, however, disclose the time window over which netflow is aggregated, which is a meaningful behavioral gap.

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 short sentences, purpose first and cost second, with no filler. Every clause carries information an agent needs.

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 a 1-parameter schema, full coverage, an output schema present, and the cost disclosed, the definition is nearly complete for a read-only analytics tool. The one omission is the aggregation window for netflow, which an agent would need to interpret results correctly.

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 the single token_address parameter is fully described there. The description restates the accepted chain formats but adds no syntax or constraint details beyond the schema, so 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?

Names a specific verb and resource — whale/institutional wallet net inflow and outflow — plus the two supported chains (Solana SPL, Base ERC-20). It implicitly distinguishes itself from trade-level siblings like rugshield_smart_money_dex_trades by focusing on net flow, but never names an alternative directly.

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 only implied by the 'netflow' framing; there is no explicit statement of when to pick this over rugshield_smart_money_dex_trades or rugshield_tgm_who_bought_sold. The cost note hints at a pay-per-call context but gives no routing guidance.

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