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

Annotations already indicate readOnlyHint=true and openWorldHint=true, covering safety and data volatility. The description adds the 100-token limit and use-case context but doesn't disclose behavior like data freshness, rate limits, or what 'statistics' specifically includes. The description does not contradict 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?

The description is very concise—three short, bullet-like lines. The key capability (statistics for up to 100 tokens) is front-loaded, and every sentence adds value. No wasted words.

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 tool has only 3 parameters (2 required), full schema descriptions, annotations, and an output schema, the description is sufficient for most use cases. It covers the core constraint (max 100 tokens) and typical usage scenarios. It doesn't explain edge cases or error handling, but that is acceptable given the supporting structured fields.

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%, so the baseline is 3. The description lists parameters blockchain, mints, and wallet_type in a summary line, which adds little beyond the schema. It does not explain format constraints like token address length or blockchain-specific wallet availability, which are already in 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 clearly states the tool provides statistics for up to 100 tokens in one request. It identifies the resource (tokens) and action (compare/get statistics). While it distinguishes from sibling compare_wallets, it doesn't explicitly differentiate from get_token_stats or get_analytics, which could also provide token statistics.

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 description suggests two usage contexts: shortlists and following up on the most-traded analytics view. However, it lacks explicit guidance on when not to use this tool (e.g., for single token stats or historical data) and doesn't mention alternatives like get_token_stats or get_analytics.

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