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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, and the description adds real context beyond them: the default thresholds, the data-limitation warnings (large buys only, FOMO users only, no trade sizes), and the interpretation of pumppill_read including that 'none stored' is a gap rather than a clean result. It stops short of stating auth/rate-limit behavior, which keeps 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 dense sentences with no filler; the core concept is front-loaded and caveats follow. It is long but each sentence adds information (scope, output shape, limitations), so the size is defensible even if slightly heavy.

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 does the work of explaining the return shape (latest/first buy, market caps, how many traders still in, pumppill_read per token), which is what an agent needs. For a parameterized read query with annotations covering safety, the only real gap is the unexplained limit parameter.

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 must carry parameter meaning. It partially does: 'default 3 traders in 60 minutes' pins min_traders and window_minutes defaults, and 'Robinhood Chain and Solana' hints at the chain values. However, 'limit' is never mentioned and the chain value syntax (free string vs enum) is left ambiguous.

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 (tokens bought by several distinct FOMO traders inside a window) and scopes it to two chains, so the agent can tell what it returns without opening the schema. It does not name or contrast any sibling (e.g. fomo_trader, whats_moving), so the differentiation is implicit rather than explicit.

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 implied by the description of what the data is (tokens multiple traders are converging on), but there is no explicit 'use this when' or 'prefer X instead' guidance against the 25 sibling tools. The caveat about FOMO's large-buys-only feed hints at when the data is appropriate, but the agent must infer it.

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