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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'read-only and informational' is largely redundant. The description does add real value by explaining that outputs include derived heuristic labels (risk score, holder type, cluster flags via common funder or frequent transfers), which signals these are computed judgments rather than raw chain data. It omits cost, rate limits, and latency for an open-world chain-querying 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?

Front-loaded with the core action and resource, then the payload, then the disclaimer. It is a single dense sentence that borders on run-on with the chained 'and ... plus ...' clauses, but every clause conveys distinct output information and nothing is padded.

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 carries the burden of explaining return values and does so thoroughly (share of supply, holder type, risk score, cluster flags, concentration figures). For a simple two-parameter read tool this is nearly complete; the gap is routing context relative to the two sibling tools that also surface risk information.

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% with explicit descriptions for both params, so the baseline is 3. The description goes slightly further by framing the response as 'largest holders' with a default ordering, which gives the limit parameter meaning beyond its numeric bounds. It does not describe the mint address format, but the schema already does.

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 verb and resource ('Lists the largest holders of a Solana token by mint address') and enumerates the returned fields: supply share, holder type label, risk score, cluster flags, concentration summary. That is far more specific than a title restatement. It never names or contrasts with siblings like check_token_safety, so differentiation is implicit rather than stated.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. 'Read-only and informational; not financial advice' is a scope disclaimer, not a routing rule, so an agent gets no help deciding between this and check_token_safety when both mention risk.

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