Live radar (free)

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

Annotations already cover safety (readOnly, idempotent, destructive=false, openWorld), so the bar is lower. The description nonetheless adds meaningful behavior: 5-second refresh cadence, list sizes (ten each), the ranking signals, and the free-vs-paid relationship. It stops short of describing rate limits or failure modes, but for a no-argument read tool this is solid added context.

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 free designation and the two result sets, and every clause carries information (age thresholds, buy threshold, probabilities, cadence, count). The first sentence is dense and slightly run-on, but no sentence is wasted.

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 must convey the return shape, and it does: two ranked lists of ten, each entry carrying the paid check URL and tool. The only minor gap is that exact field names/structure of a list entry are not spelled out, which is acceptable given the per-entry description.

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?

Zero parameters, so the baseline is 4 per the rubric. The description reinforces this with 'No arguments,' which removes any ambiguity about needing inputs.

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 states a specific verb+resource: it returns two ranked lists of covered pump.fun mints (<30s by rug probability, <15min with >=5 buys by graduation probability). It also differentiates itself from the sibling check_pumpfun_risk, so an agent can tell these apart without opening schemas.

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 routing: 'Use it to find fresh mints worth a paid check; for a mint you already hold call check_pumpfun_risk.' It names both the when-to-use condition and the specific alternative tool for the adjacent case.

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