get_trending_tokens

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 that no authentication is required and that results are sorted by volume and price change, but it says nothing about pagination, rate limits, or result shape. For a read-only listing tool this is adequate but thin.

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 the purpose, with no filler. Efficiency is good, though 'No auth' is slightly abrupt and the description is arguably under-specified rather than concise.

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?

With 5 optional parameters, no annotations, and no output schema, the description should carry more weight. It omits default behavior for limit/period, what 'chain' accepts (string or number), and what a returned token record contains.

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 only 60%: chain, minVolume, and minLiquidity have schema descriptions, but 'limit' and the period enum do not. The description adds no parameter meaning at all — the sort criteria it mentions correspond to no parameter — so it fails to compensate for the documentation gap.

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?

The description gives a specific verb+resource ('Get trending tokens') plus the sort criteria (volume and price change), so the operation is unambiguous. It does not, however, distinguish this tool from close siblings like get_top_tokens, get_newest_tokens, or get_bigbuys, leaving an agent to guess which 'list tokens' tool applies.

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 guidance on when to use this versus get_top_tokens, get_newest_tokens, or get_bigbuys, and no conditions or prerequisites are stated. The only usage-relevant signal is 'No auth,' which tells the agent it can call this without credentials but does not help it choose between sibling listing tools.

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