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

Annotations already cover read-only/idempotent/non-destructive, but the description adds real behavioral context: newest-first ordering, inclusion of losers, a tiered access model with delay_minutes, and a warning that a count of calls is not a success rate. It stops short of rate limits or auth details, but adds meaningful disclosure beyond the annotations.

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?

The core purpose is front-loaded in the first sentence, and each subsequent sentence adds usable information. Parenthetical asides make it slightly dense, but there is no 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 usefully enumerates return fields and ordering, which is a meaningful contribution. However, it leaves the three input parameters essentially undocumented, so an agent cannot know how to scope days, chain, or limit from the description alone.

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 0% for three parameters, so the description carries the full burden but explains almost none of them. It implies chain values (Solana, Robinhood Chain) and newest-first ordering, yet never clarifies days, limit, or the chain filter.

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 states a specific resource and scope: the calls PumpPill's room posted on Solana and Robinhood Chain, with the fields each call carries. It is clearly distinguishable from vague siblings, but it never names an alternative tool to route against, so it stops short of full sibling differentiation.

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 when-to-use guidance, no condition selecting this over premium_calls_recent or outcomes_measured, and no stated prerequisites. The access-delay note describes visibility, not when an agent should call this tool.

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