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

Annotations cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds a genuinely non-structured trait: a fixed cost of 1 credit, which an agent needs for budgeting decisions. It does not disclose result limits, freshness, or rate behavior.

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 short sentences, front-loaded with what the tool returns and the cost, followed by an actionable tip. No filler or redundancy.

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?

No output schema exists, yet the description never characterizes the return payload (fields per token, count/limit, ordering). Cost and the sibling workflow are covered, so it is viable for a simple list tool but leaves the agent guessing about result shape.

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?

The single parameter (api_key) has zero schema description coverage, so the description would need to compensate and does not mention authentication at all. The parameter name is largely self-explanatory, but there is no hint that a key is required or that register_free_key/check_credits siblings exist to obtain one.

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 (boosted/trending Solana tokens) and its source (DexScreener), which no sibling claims. The differentiation from scan_token is implied via the workflow tip rather than stated outright, and the retrieval verb ('latest') is mild.

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?

Sets clear context (surfacing trending candidates) and recommends a concrete follow-up: 'scan_token any candidate before trading.' It does not state when NOT to use the tool or contrast it with scan_tokens (plural), but the workflow positioning is explicit enough to route an agent.

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