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

Annotations already cover the read-only, open-world, non-destructive profile, yet the description adds two behaviorally relevant facts: the data is scrubbed for prompt-injection in token metadata (a safety guarantee) and the call carries a $0.003 USDC cost. The cost disclosure is genuinely useful context an agent needs before invoking.

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 compact sentences with the resource front-loaded. The second sentence is short but its 'Price: $0.003 USDC on Base' framing is ambiguous and arguably misplaced in a tool description.

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?

An output schema exists, so return values need not be explained, and the safety/cost behavior is covered. However, for a paid screening tool in a crowded trending-token family, the description lacks the usage guidance needed to pick it correctly over siblings.

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 are zero parameters (schema coverage 100% trivially), so the baseline for no-param tools applies and the description has nothing to add. Nothing here is misleading about 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 verb+resource: 'Top trending Solana tokens', with a screening pipeline named (DexScreener + CanaryGuard scrubber). The 'Solana' qualifier implicitly separates it from base_trending_tokens and base_new_pools, but no sibling is named explicitly, and the trailing 'Price: $0.003 USDC on Base' confuses rather than clarifies what the tool returns.

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 when-to-use guidance, no when-not-to-use, and no routing to alternatives, despite five or more sibling tools covering related trending/crypto data. The 'via DexScreener' and 'scrubber' clauses describe mechanism, not selection criteria.

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