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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds meaningful context beyond that: the data is delayed by delay_minutes, the exit-rule record spans 28 days, and losers are explicitly included (no survivorship bias). The closing 'A record, not a prediction' usefully sets expectations about the nature of the output.

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 return shape is front-loaded, followed by two short clarifying sentences. The single long first sentence is dense but every clause adds distinct information. No filler or redundant restatement of the title.

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?

There is no output schema, so the description must describe returns, and it does: per-call market cap at call/now, the move since, and a 28-day exit-rule record. For a 1-parameter read-only tool this is largely complete, with the only gap being the unstated default and the ambiguous role of delay_minutes.

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?

With a single parameter at 0% schema coverage, the description carries the burden. It supplies the valid range (1-168) for `hours`, which the schema does not, but omits the default value of 48. Mentioning `delay_minutes` alongside the input param risks mild confusion about whether it is an input or an output field.

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?

States a specific verb and resource: returns PumpPill's Ignition momentum calls posted within the last `hours`, along with market cap at call/now and the move since. This is clearly distinguishable from generic siblings like best_calls or premium_calls_recent by the 'Ignition' scope and the exit-rule record. It stops short of naming which sibling it replaces, so it is not 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?

There is no explicit when-to-use guidance and no alternative tool is named. The line 'Calls reach this tool after a delay... members get them live in Telegram' hints that this is a delayed record versus a live feed, but that is context about data freshness rather than a routing rule for the agent choosing among ~37 siblings. Usage is only weakly implied.

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