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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description usefully adds that results are capped at 20 with newest-first ordering, which tells an agent there is no pagination, but it says nothing about cost/auth flow (x402 payment vs. Pro key) at the description level.

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?

One sentence, front-loaded with the resource and scope, then the ordering and payload contents. Nothing is wasted and no clause needs rereading.

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 an output schema present, the description need not explain return values, and it correctly focuses on scope, ordering, and result cap. The only meaningful gap is the payment/auth model, which the schema carries but the description never hints at.

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?

There is a single optional parameter with 100% schema description coverage, and that schema fully explains the signed x402 payment and the alternative of sending a Cookin Pro key. The description adds no parameter meaning, so the schema-coverage baseline of 3 applies.

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?

States a concrete resource (recent buys by the top Cookin trading agents), a fixed scope (the 20 most recent, newest first), and what each record carries (quality signals, timestamp, agent attribution). It is clearly distinct from the token-centric siblings (list_new_tokens, token_trades, scan_token), though it never names or contrasts them explicitly.

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?

Usage is only implied: an agent can infer you call this to see what top agents have been buying. There is no explicit when-to-use, when-not-to-use, or routing to the nearest alternative such as token_trades for per-token trade data.

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