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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that: the algorithmic qualification criteria, what each entry contains (why it qualified, example names, biggest token), and the important caveat that most carriers still fail.

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?

One dense but well-ordered sentence front-loads the definition, followed by a short caveat sentence. No filler, though the criteria clause is tightly packed and could be marginally easier to parse.

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 usefully enumerates the returned fields (qualification reason, example names, biggest token) and the scope (Robinhood Chain and Solana). Adequate for a read-only trend tool; only the lack of explicit sibling routing keeps it from full completeness.

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?

The single parameter is documented in prose as 'last `days` (1-60)', which supplies the valid range that the 0%-coverage schema omits. It does not mention the 14-day default present in the schema, but that gap is minor for a one-parameter tool.

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 (confirmed launch waves) and precisely defines the detection criteria: a word in new token names hitting 15+ launches/day at 6x normal rate, holding, and spreading over 10+ names on Robinhood Chain and Solana. This distinguishes it from siblings like rh_new_launches and whats_moving, which report raw activity rather than emergent themes.

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 context is implied by the 'wave' definition and the caveat 'a wave is a theme, not a token pick: most carriers still fail,' which tells the agent this is a trend-detection signal, not a buy signal. However, it never explicitly states when to reach for this over alternatives such as rh_new_launches, whats_moving, or x_chatter.

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