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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds only a vague hint that results carry 'quality signals and holder behavior'; it says nothing about result volume, freshness/refresh cadence, or the payment flow implied by x_payment.

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?

It is a single short phrase with zero filler, and the distinguishing qualifier ('currently pumping') is front-loaded. Its brevity is efficient, though it borders on under-specification rather than optimal concision.

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?

An output schema exists, so return values need not be explained, and there is only one optional, fully-documented parameter. For a read-only list tool this is close to adequate, but the absence of any routing versus sibling listing tools leaves a real gap.

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 100% and the single x_payment parameter is fully documented in the schema, including the Cookin Pro key alternative. The description contributes no additional meaning about that parameter, so the baseline of 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?

The fragment 'Pump.fun tokens currently pumping' names a specific resource and a filter condition (currently pumping), which is enough for an agent to know what it returns. It does not differentiate from siblings like list_new_tokens or list_graduated_tokens, so an agent cannot tell from the text alone which listing to pick.

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 exclusions, and no named alternative among the several sibling list tools. The 'currently pumping' qualifier implies usage but leaves the choice between list_new_tokens, list_graduated_tokens, and list_agent_buys to inference.

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