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

Annotations already cover the read-only, idempotent, open-world, non-destructive safety profile. The description adds genuinely new behavioral context: the data lags ~10 minutes behind, free access returns only the newest 3 items, and an API key raises that to 30 with an x402 payment path. This is real disclosure beyond structured fields.

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?

It is short and the access tiers are front-loaded at the end, but the prose is fragmented and cryptic ('Rugged of resolved', 'every count with its N'), which costs parsing effort. Not padded, but not cleanly structured either.

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 and no parameters, the description carries the burden and mostly succeeds: it explains the two data modes, staleness, and access limits. It would be stronger if it stated the return shape more plainly or contrasted with the sibling KOL tools.

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 tool takes zero parameters, so per the rubric the baseline is 4. Nothing in the schema needs compensating, and the description's mention of 'One call' is consistent with a parameterless interface.

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 conveys the resource (a feed of KOL/top-profit wallet launches and their subsequent rugs) via the 'JUST IN' / 'AGAIN' breakdown, so the content is decipherable. However, the framing is jargon-heavy and elliptical ('Rugged of resolved', 'every count with its N'), and it never distinguishes this feed from the sibling groundtruth_kol_board or groundtruth_time_to_rug.

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 notes a free tier (newest 3) versus an API-key tier (30, or x402 over /v1/kol/feed), which is access guidance, but it gives no when-to-use-this-vs-alternatives direction and no exclusions. An agent cannot tell from this text why it would pick this feed over the KOL board or time_to_rug.

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