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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds real value by disclosing the ordering and the conditional presence of AI summaries ('when one exists'). It stops short of noting pagination, result totals, or how 'detected' events are qualified.

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?

A single sentence, front-loaded with what the tool returns before the field enumeration. The long listing of metrics earns its place because no output schema exists, though it reads as a run-on rather than a structured list.

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 carries the burden of describing return content and does so thoroughly, and annotations cover safety. Gaps are minor: no mention of whether results are limited by available data, deduplication, or how to page beyond the limit.

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 all three parameters (days, limit, language) are already documented with defaults and bounds. The description only indirectly touches them by mentioning AI summaries, which hints at the language parameter, 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 resource (detected pump and dump events) with an explicit scope (Binance futures) and ordering (newest first). The enumeration of returned fields makes it unmistakable against siblings such as get_liquidation_levels or get_order_book_walls, which cover entirely different market phenomena.

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?

There is no guidance on when to reach for this tool versus the four sibling signal tools, nor when-not to. 'Newest first' describes output ordering rather than selection criteria, and nothing tells the agent how to choose days or limit.

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