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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, but the description adds meaningful context: free access is limited to the top 3 rows per list and list totals, while an API key (or /v1/kol over x402) unlocks every row. It also discloses that output contains wallets only and never names, and lists the data sources, which goes well beyond the 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 first sentence front-loads the core idea, but the rest is a dense run-on of sentence fragments and jargon that is hard to parse. It contains useful detail, yet the structure could be much cleaner and less repetitive without losing meaning.

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?

Given the tool's complexity, no output schema, and zero parameters, the description supplies substantial context: data sources, counted fields, free/paid tiering, and the no-names constraint. It still omits ordering, pagination, and any explanation of what 'list juice' or 'seconds to the pull' mean operationally, which keeps it from being fully complete.

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 the baseline is 4. The description does not need to explain parameter syntax, and it instead uses the space to describe the output fields (tag, launches, rugged/resolved, PULL, bonded, last mint, list juice), which is appropriate for a no-param tool.

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 and resource: it reports what KOL wallets launched and how those launches ended, with named metrics. It does not, however, explicitly differentiate itself from siblings like groundtruth_kol_feed or groundtruth_time_to_rug, leaving the agent to infer the 'board' framing from the tool name alone.

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?

There is no explicit when-to-use guidance or comparison to alternative tools. The phrase 'One call' hints that this tool is a single aggregated request, but the description never states when an agent should choose it over groundtruth_kol_feed, groundtruth_scoreboard, or similar siblings.

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