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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds a genuinely decision-relevant trait the annotations lack: a fixed 0.010 USDC per-call cost with the supported payment networks. It does not describe latency, rate limits, or failure behavior, but the cost disclosure is the key missing piece an agent needs before calling a paid tool.

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 with the capability front-loaded and the cost constraint second; every clause carries information and nothing is padded.

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 cost is disclosed. However, for a paid tool sitting among several overlapping audit/screener siblings, the definition never resolves which one to pick or whether it works on non-trending tokens, leaving a real selection 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?

Schema coverage is 100%, so the token_address format for Base ERC-20 and Solana SPL mints is already documented in the schema. The description reinforces the two supported chains but adds no format, validation, or edge-case detail beyond the schema; 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 (screens) and resource (trending Solana/Base tokens) and enumerates the metric families it bundles: honeypot, tax, liquidity depth. It is distinguishable from single-metric siblings like check_honeypot only by inference from the metric list, not by an explicit contrast.

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?

No statement of when to use this composite screener versus the overlapping siblings rugshield_pre_swap_scan, check_honeypot, or analyze_liquidity, and no prerequisites or exclusions. The only implied usage cue is that it targets 'trending' tokens, which is not elaborated.

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