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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description surfaces a real capability constraint the agent must know: wallet_type availability varies by chain (solana has kol/smart/whale, bnb/base/rh have kol and smart, eth has kol only), and the window is hard-capped at 24 hours. It does not discuss auth or rate limits, but the value added over the annotations is substantive.

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 leads, then a compact parameter listing — no filler sentences and every line carries information. The 24-hour cap, the single-token scope and the defaults are all front-loaded where an agent will see them.

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 4 parameters, one required, full schema coverage and an output schema present, the description need not explain return values. It supplies purpose, when-to-use and the chain/wallet_type constraints, leaving only minor gaps such as pagination or whether counts are truncated.

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 the schema already documents every parameter including defaults, ranges and the per-chain wallet_type matrix. The description largely restates the same parameter list, adding only the shorthand enumeration of chains and types — marginal value over structured data, so baseline 3.

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 states a specific measurement ('how many trades happened and how much value moved over a window of up to 24 hours, plus how many distinct wallets') — verb, metric set and resource are all concrete. It also explicitly positions itself against trade-level tooling ('rather than for the individual trades'), so an agent can separate it from get_recent_trades without reading either schema.

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 gives a clear selection rule: use it to gauge how busy a market or a single token is, not to inspect individual trades. That is a genuine when/when-not pair, though it never names the concrete alternative tool (get_recent_trades) the way a 5 would.

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