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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description adds only 'right now', which weakly signals live/recency semantics; it says nothing about result ordering, pagination, rate limits, or data freshness, which matter for an open-world trending feed.

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?

One short sentence with no filler and the key qualifier front-loaded, so it is efficient. The problem is under-specification rather than verbosity: the brevity is bought at the cost of the enum and parameter information an agent needs.

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 no output schema and 0% schema description coverage on two parameters, the description is the only place semantics could be explained, and it covers only the default 'trending' case. An agent cannot tell what the return shape is or what 'new' and 'top' produce, which is a real gap for a tool with an enum and a bare numeric id.

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 0%, so the description must carry the parameter burden and it largely fails. It hints that a chain is involved (mapping loosely to chainId) but never says whether chainId is a numeric network id versus a name, and it completely ignores the 'list' enum, leaving 'new' and 'top' undefined while implying only 'trending' exists.

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 fragment identifies the resource (tokens) and a qualifier (trending right now on a chain), so an agent can guess it returns a ranked token list. But it uses no verb and never acknowledges that the same tool also serves 'new' and 'top' lists, so the stated purpose is narrower than the tool's actual behavior. It also does nothing to distinguish it from sibling search_tokens.

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 when-to-use guidance, no mention of when to prefer search_tokens or price_history, and no stated prerequisites. The only implicit signal is 'on a chain', hinting a chainId is needed, which the schema already enforces as required.

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