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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely non-obvious behavioral context: 'free' implies a paid tier boundary, `checks` lists numbers that failed a sanity check and must never be quoted, and `summary` is the quotable paragraph. It does not state rate limits or response size, which keeps it at 4 rather than 5.

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-loaded with the resource and scope, and every clause maps to a real payload section. The long semicolon chain of contents is dense and slightly hard to scan, but no sentence is filler and the operational warnings (`checks`, `summary`) come after the payload inventory where they belong.

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 no output schema, the description carries the return-shape burden and does so by enumerating the payload sections and flagging the two special fields (`checks`, `summary`) that change how an agent should report results. Only the precise key names and nesting of each section are left implicit, which is a minor gap for a read-only aggregate.

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?

Only one parameter and schema coverage is 100%, so the schema already defines the format and the 'default the latest' behavior. The description restates 'one UTC day' and the default but adds no syntax, edge-case, or timezone-caveat detail beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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?

Names the resource and scope precisely ('Pump.fun stats for one UTC day') and then enumerates the exact payload: launches, graduations, graduation rate, SOL/USD volume, traders, top coins by peak market cap and volume, deployer leaderboard, instant/fastest graduations, hourly rates, and dead launches. The final clause distinguishes it from the paid per-entity siblings (launch_record, deployer_record), so an agent can tell it apart without opening a 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?

The 'For:' clause gives concrete trigger phrasings ('pump.fun today or yesterday, how many coins launched...'), which is stronger than most. It also routes deeper follow-ups to launch_record and deployer_record. It stops short of naming when NOT to use it relative to other day/range siblings like base_rate or launches_since, so it falls short of explicit exclusion guidance.

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