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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: trades are read from the chain as they land (live, incremental), ordering is oldest first, and the call is free. No mention of rate limits or failure modes, which keeps it short of 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?

Front-loads 'Free' and the scope in one dense sentence, then the wallet filter, then the use cases, then the handoff to siblings. The long first sentence is a run-on but every clause carries information; nothing is filler.

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 no output schema, the description takes on return-value disclosure and does it well by enumerating wallet, coin name/symbol/mint, side, SOL, USD and market cap at trade. The time window and default threshold are also given. Only minor gaps remain, such as what happens when no trades match.

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 description coverage is 100%, so the schema already explains side, limit, since, wallet and min_usd. The description restates the wallet scoping and the $2,500/$1,000 threshold rather than adding new syntax or edge-case meaning, 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?

States a specific verb and resource: every pump.fun buy/sell of $2,500+ in the last hour, read from chain, oldest first, with the exact fields returned. An agent can immediately tell this apart from check_coin, wallet_records, or top_wallets.

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?

Gives explicit triggering questions ('what are whales buying', 'did this wallet buy or sell') and explicitly redirects: 'A record of what wallets did, not a signal; then check_coin on a mint, wallet_records on a wallet.' Both the when-to-use and the alternatives are named.

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