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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond that: it runs three underlying analyses, returns an actionable verdict, and discloses pricing and the free tier. No contradiction with annotations.

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?

The description is compact and front-loaded: the first sentence states the core value proposition and output, the second explains composition and cost advantage, and the third gives pricing. Every sentence earns its place with no filler or redundancy.

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?

For a single-parameter, read-only tool with no output schema, this description is complete enough: it enumerates the returned dimensions (score, risks, graduation odds, dev record, snipers, holders, flow), the verdict scale, the bundled nature, and cost. An agent has sufficient information to decide when and how to call it.

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?

The input schema already documents the only parameter, mint, with a description and a validation pattern, giving 100% schema coverage. The description reinforces that the target is a pump.fun launch but does not add new parameter-level meaning, so the baseline of 3 is appropriate.

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 description clearly identifies a composite action: it runs pump_token + pump_dev + pump_odds together and produces a single 0-100 score with positives, risks, and a categorical verdict. This distinguishes it from the sibling individual tools by framing it as the bundled, one-call option.

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?

It gives clear usage context: use this when you want one integrated verdict across the bundled analyses, especially because it is 'cheaper than calling them separately.' It names the component alternatives but stops short of explicitly saying when to prefer the individual tools instead, so it lacks full when-not guidance.

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