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

Goes well beyond the annotations by disclosing the cost model ($0.002/call, 10 free/day, x402 options on payment-required results) and error semantics (isError with a message, not charged). It also explains that early flow is pre-aggregated so no chain replay is needed, which materially shapes how the agent uses the result.

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?

Four compact sentences front-loaded with purpose, then the use case, then cost, then error behavior. Every sentence carries information an agent needs (pricing and error semantics are not optional for a paid tool).

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-value explanation is not required; the description still covers the key operational facts — freshness, result cap, cost, and failure behavior. Nothing needed to call this correctly is missing.

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%, so both parameters (limit, window_s) are already fully documented with ranges and defaults. The description alludes to the window conceptually ('first-N-seconds flow already aggregated') but adds no syntax or format detail beyond the schema — baseline 3.

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 resource (newest pump.fun tokens) and enumerates the returned fields (dev buy, early buyers/volume, curve progress, market cap, creator launch count), plus the freshness bound ('seconds old') and cap ('up to 50'). An agent can distinguish this discovery-listing tool from siblings like pump_history and pump_token.

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?

Explicit 'When to use: To discover new mints' with a concrete follow-on step routing to launch_scan for a verdict. It does not, however, say when to prefer a sibling such as pump_pulse or pump_history instead, so the alternative-selection guidance is only partially covered.

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