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

With readOnlyHint and openWorldHint already declared, the description still adds real value: data sources (EVM public-RPC logs, ~10k-block window, RugCheck for Solana), the presence of a dev-selling alert, and the requirement to surface the `display` markdown with images. It omits rate limits and truncation behavior for the block window, keeping it off a 5.

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?

Three sentences, front-loaded with the core behavior, then the output-display instruction, then cross-tool routing. The swap upsell is tangential to invoking this tool but is framed as workflow guidance, so it mostly earns its place.

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?

There is no output schema, and the description does the minimum by noting the `display` markdown field the agent must render. It does not characterize the payload shape (transfer list, holder table, alert flags) and leaves one of three parameters unexplained, so it is adequate but not complete for a moderately complex analysis tool.

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 only 33% and the description compensates poorly: chainId is fully documented in the schema, but `minUsd` is never explained (only obliquely implied by 'large recent transfers') and `address` semantics are left entirely to the schema's length bounds. An agent must guess what minUsd filters and in what units.

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 names a specific resource and scope: large recent token transfers from EVM public-RPC logs over the last ~10k blocks, with buy/sell labeling against DEX pools, deployer/owner data, and a Solana holder/creator path via RugCheck. It is concrete enough to separate from token_risk or scan_movers, though it never explicitly contrasts itself with those siblings.

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 next-step instruction (offer a SwapChan swap via get_quote or swapUrl) and routes the agent to swapchan_playbook for cross-tool workflows. It does not say when to prefer this over token_risk, scan_movers, or find_money, so the selection decision against the closest siblings is left to inference.

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