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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the bar is lower. The description still adds real context beyond them: the 2-hour freshness window, the automated verdict behavior, and the $0.003 USDC per-call cost on Base. It stops short of explaining edge cases such as pools with missing verdicts.

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?

Two tight sentences, front-loaded with the resource and scope, followed by the distinct value-add and cost. Every clause earns its place, including the pricing disclosure which is genuinely useful for an agent deciding whether to call.

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, return format needn't be described, and with zero parameters there is no input surface to document. The description covers scope, verdict and cost, but does not explain what the TRUST/BLOCK verdict signifies or the volume/rate of pools returned, leaving a small gap.

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?

This tool takes zero parameters, so the baseline expectation is 4 and there are no parameter semantics to clarify. The description correctly avoids inventing or implying any 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?

States a specific resource (newly created Base liquidity pools), a precise time scope (last 2 hours), and a distinctive value-add (automated TRUST/BLOCK verdict). An agent can tell it apart from siblings like base_trending_tokens or solana_trending_safe without opening any schema.

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?

The description never says when to reach for this tool versus alternatives such as base_trending_tokens or the Solana equivalent. It implies a monitoring use case but offers no explicit context, exclusions, or sibling routing.

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