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

Annotations already declare readonly/idempotent/non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the returned dataset (price, liquidity, volume, 24h change) and a per-call cost of $0.01, which is actionable for an agent deciding whether to invoke it.

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?

A single tight sentence with zero waste: resource and default scope first, then returned fields, then cost. Everything earns its place.

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?

For a read-only list tool with no output schema, the description covers scope, default chain, the fields returned, and the cost, while the schema fully documents both optional params and annotations cover safety. Nothing needed to call it correctly is missing.

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?

Schema description coverage is 100%, so both parameters are already documented ('chain' id and default, 'limit' max 50). The description only reiterates the chain default, adding no format or syntax detail beyond the schema — the baseline 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 specific verb+resource ('currently trending token pools') plus the chain scope and the data fields returned (price, liquidity, volume, 24h change). It is clearly a discovery/list tool, distinct from price-checking or snapshot siblings, though it does not explicitly contrast itself with near neighbors like get_recent_launches or get_token_snapshot.

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 implied ('default Solana or any supported chain via chain'), giving enough to invoke correctly, but there is no explicit when-to-use versus alternatives or when-not-to-use guidance relative to the many token siblings.

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