New pump.fun launches with rug odds ($0.001)

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

Goes well beyond the annotations by disclosing the pricing model ($0.001 per poll, empty pages cost the same), the achievable poll rate (~20 launches/min), and that a stale feed is refused before payment. These are non-obvious cost and failure behaviors an agent must know before calling.

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 the cost, then usage, then payload, then routing, in one dense paragraph with no filler sentences. It is information-heavy and slightly packed, but every clause carries operational value.

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, yet the description enumerates the returned item fields (creator, reserve, buys, buyer inflow, top-5 holder/creator shares, first-observed flags, verdict, P(rug within 300s), P(graduation)), so an agent knows what to expect without a schema.

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 already 100%, so the baseline is 3, but the description adds real meaning: default window of 60s, hard cap of one hour, and that `since` should carry the previous call's next_cursor. It loosens rather than restates the schema.

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 (poll/return) and resource (covered pump.fun launches after `since`), with ordering (oldest first), cap (up to 100), and the exact payload carried by each item. It clearly differentiates itself from siblings by naming recent_launches for one-off screens and check_pumpfun_risk for a single mint.

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 says when to use it ('when a bot polls for new pump.fun launches') and routes the two adjacent use cases to named alternatives (recent_launches, check_pumpfun_risk). It even prescribes the polling loop via 'pass next_cursor back as since'.

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