getTopTokens

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) indicate a safe, read-only operation. Description adds that results include enriched metadata and multi-timeframe metrics (24h, 1h, 5m), which is useful behavioral context beyond annotations.

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 concise sentences plus a clean list of required/optional parameters. No filler, every sentence adds value. Front-loaded with purpose.

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?

Given the presence of an output schema (not shown but indicated), the description adequately covers the tool's functionality for a complex, multi-parameter tool. It mentions ranking criteria and timeframes. Could briefly note pagination behavior, but overall complete enough.

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% (all parameters described in schema). The description repeats required/optional status but does not add new semantic information beyond what the schema already provides (e.g., field descriptions, enums). Baseline of 3 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?

Clearly states the tool retrieves top tokens on a network, ranked by volume, price, liquidity, or activity. Distinguishes from siblings like getTokenDetails (single token) or filterNetworkTokens (filtering).

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?

Explicitly lists required (network) and optional parameters (page, limit, sort_by, etc.). Provides implicit guidance by stating the ranking criteria, but lacks explicit conditions for when to use this versus other tools (e.g., getTokenDetails or filterNetworkTokens).

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