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

Annotations already declare readOnly, openWorld, non-destructive. The description adds that results are on-chain and include concentration analysis, which is useful context beyond annotations. However it doesn't disclose return shape, limit cap (schema shows max 20), or pagination/data freshness, so it's modest value over 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?

Two tight sentences: purpose first, then routing to the alternative. No filler; every clause earns its place.

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 annotations cover safety and the tool is a simple read with 1 required param, the description is nearly complete. Minor gaps: limit cap and network option are only in schema, and no output schema exists, but for a read tool of this simplicity that's acceptable.

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 0%, so the description must compensate. It clarifies the 'mint' target (a token) and the nature of results (holders + concentration), and 'limit' is inferable as count of top holders from 'top holders'. Network/limit semantics are not fully spelled out, so not a 5.

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?

States a specific resource (top holders of a token) with an added analysis dimension (concentration), and explicitly distinguishes from get_token_details (price/volume) by name. An agent can pick between them without opening either schema.

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?

Gives an explicit use case (check concentration before buying) and names the sibling + condition for the alternative (price/volume → get_token_details). Explicit when-to-use and when-to-use-instead.

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