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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds real context beyond that: the data provenance (own collector, ~1350 alerts/day) and the three possible ACO decisions (WATCH_ENTER / EXIT_IF_LONG / AVOID), which tells the agent this is a pre-computed signal feed rather than raw on-chain data. It does not mention rate limits, pagination, or behavior when no alerts match, keeping it from 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-loaded with the core purpose and data source, then a compact Args block — no wasted sentences. The '(1350+ alerts/day)' figure and the disclaimer are mildly promotional but arguably earn their place for a financial-signal tool.

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-value explanation is not required, and the description still names the key fields. Provenance, decision vocabulary, and both parameters with their ranges/enums are covered. Missing only the semantic meaning of the alert_type values and what an empty result looks like.

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 0%, so the description carries the burden and largely succeeds: it gives the minutes lookback range (5-720), which the schema's bare integer does not, and enumerates the five alert_type values the schema omits entirely. What it does not do is explain what each alert_type means (ignition vs sudden_flow vs pre_pump), so an agent still guesses which filter to pick.

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?

Specific verb+resource: 'Returns recent alerts' from a named pump.fun/Raydium behavioral collector, plus the exact fields returned (flow multiplier, smart-buyer count, per-alert decision). An agent knows precisely what data comes back. It does not explicitly differentiate from plausible siblings like get_signals, get_smart_money_feed or get_trading_decision, so it stops short of a 5.

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 'Live pump.fun detection alerts' — there is no statement of when to prefer this over get_signals / get_smart_money_feed / get_trading_decision, and no exclusions. The 'Not investment advice' line is a disclaimer, not routing guidance. An agent can infer the domain but must guess at boundaries with siblings.

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