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 implies a read-only fetch ('Get') and discloses the shape of the returned data, but says nothing about data freshness, rate limits, auth requirements, or whether results are cached — meaningful gaps for an unannotated tool.

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 compact sentences with the purpose front-loaded and no filler. The 'Requires: exchange, symbol' clause is mildly redundant with the schema's required array, costing it the top score.

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, the description must describe return values and it does so adequately by naming the four data categories. Parameter documentation is fully handled by the schema; only the absence of safety/behavioral context keeps it from a 5.

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% (both 'symbol' and 'exchange' are documented inline), so the baseline is 3. The description only repeats that these two parameters are required and adds no format, casing, or ID-resolution detail 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 states a specific verb and resource ('Get comprehensive research data for a token') and enumerates the payload (grade, liquidity metrics, risk assessment, percentile rankings), so the agent knows what it returns. It does not, however, differentiate itself from close siblings such as get_token_intel or get_stats, which appear to cover overlapping ground.

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 instruction is 'Requires: exchange, symbol,' which restates the schema's required fields rather than telling the agent when to pick this tool over get_token_intel, get_price_stats, or get_stats. No exclusions, prerequisites, or alternative-routing guidance are given.

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