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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the up-to-50-row cap, that flow is pre-aggregated for the first N seconds, per-call pricing with a free tier and x402 payment-required behavior, and error semantics (isError, invalid input or upstream failure not charged). That is exactly the extra behavioral detail annotations cannot express.

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?

Front-loads purpose, then usage, then pricing and error behavior, with every sentence carrying information. It is dense and slightly long, but no sentence is filler; the pricing/error block is justified 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?

With an output schema present, the description need not describe return values, and it still covers freshness ('seconds old'), row cap, pricing, payment flow, error handling, and the recommended next tool. Nothing material for correct invocation 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 the schema already documents limit and window_s fully; baseline would be 3. The description lifts this slightly by explaining the semantics of the window ('the first-N-seconds flow already aggregated' / 'early-flow window after creation'), giving meaning to window_s beyond its range constraints, though it adds nothing for limit.

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 (newest pump.fun token launches) and enumerates the payload dimensions (dev buy, early buyers/volume, curve progress, market cap, creator launch count). This clearly separates it from siblings like pump_token (single token) and pump_history, so an agent can pick it without opening the schema.

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?

Explicitly states 'When to use: To discover new mints' and routes the agent to a follow-up tool (launch_scan on the MAD Synapse server) with its URL. It lacks an explicit when-not or a direct comparison to adjacent siblings such as pump_pulse, so it stops just short of full alternative coverage.

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