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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: the market-cap field comes back empty on this endpoint even for Solana, which the agent would otherwise not know. It stops short of disclosing pagination or result-size behavior.

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 lead paragraph is strong and front-loaded, but the following parameter lines duplicate what the 100%-covered schema already documents, so they don't earn their space. The market-cap caveat is a useful carve-out but the overall block is longer than needed.

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?

An output schema exists, so return values need not be explained. Between the purpose statement, the use-case anchor, the market-cap caveat, and the (redundant) param notes, an agent has what it needs to call this correctly; only edge cases like pagination or empty-result handling are unaddressed.

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 baseline is 3. The description largely restates the schema (blockchain options, mint mapping, wallet_type restrict/omit) without adding syntax, format, or edge-case meaning beyond 'omit to merge all types', which the schema already states.

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 opens with a concrete verb+resource ('Who is trading a token') and enumerates the exact metrics returned (KOL/smart/whale counts, bought/sold, buying pressure, entry times, individual positions). It explicitly differentiates from the sibling get_token_holders by noting the market-cap gap, so an agent can tell the two apart.

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?

It gives an explicit primary use case ('The main tool for "is anyone notable in this token"') and routes one specific field (market cap) to get_token_holders. However, it doesn't address the other nearby siblings (compare_tokens, get_token_transactions) or state when not to use it, so guidance is clear but incomplete.

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