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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses ranking bias against thin, new, and wash-like books and the $0.005 USDC cost, but it does not state read-only behavior, rate limits, or what the short summary contains.

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 front-load the resource and returned fields, then add ranking behavior and cost. Every sentence adds information without repetition or filler.

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 one-parameter read/list tool with no output schema, the description names the returned fields, ranking behavior, and cost, while the schema fully documents the only parameter. This is sufficient for an agent to call the tool correctly.

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%, and the single optional limit parameter is already documented in the schema as '1 to 25, default 15'. The description adds no further constraint, format, or usage detail for the parameter, so the baseline score is appropriate.

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 (Trending Solana tokens) and enumerates the data it returns: liquidity, 24h volume, pair age, risk flags, and a short summary. The sibling tools (ping, wallet_funding, wallet_profile) serve unrelated purposes, so an agent can identify this as the token-trending tool without ambiguity.

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 implies use for discovering trending tokens and notes ranking behavior for thin, new, and wash-like books, but it never states when to choose this tool over alternatives or any prerequisites. With no explicit when-to-use guidance, the usage context is only implied.

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