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

With no annotations supplied, the description carries the full burden and does disclose two useful behavioral facts: the tool is gated behind premium auth and it fuses two external sources (Google Trends, DexScreener boosts). It says nothing about rate limits, what happens on failure, or whether missing token identifiers cause errors rather than a DEAD verdict.

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?

A single dense sentence plus a lock emoji; the access constraint and the analysis scope are both front-loaded with no filler. Slightly undermined by cramming access gating into the same sentence as purpose, but overall tight.

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 three-parameter, no-output-schema, no-annotation tool, the description usefully signals the return categories and the auth requirement. It still leaves open how the optional identifiers combine and what an empty or invalid token yields, which matters given all parameters are optional.

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%, so the three parameters (chain, query, address) are already documented in the schema and the baseline is 3. The description adds no guidance on how the parameters interact — e.g., whether address alone suffices or chain is required for resolution — so nothing is gained beyond the schema.

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 names a specific analysis ('Viral potential analysis combining Google Trends data + DexScreener boost activity') and even enumerates the output tiers (DEAD, QUIET, BUZZING, VIRAL, MEGA_VIRAL), so the resource and result shape are clear. It stops short of differentiating itself from siblings such as momentum_score or token_scan, so an agent must guess at the boundary.

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 only usage constraint given is the access gate ('PREMIUM, not available anonymously on this endpoint'), which tells the agent when it will fail but not when to choose this tool over momentum_score, token_scan, or trend-related siblings. No exclusions or alternative routing are stated.

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