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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses the verdict taxonomy (ok, caution, avoid, unknown), the degradation path when the RPC cannot enumerate holders (partial results with explicit coverage and null holder sections, which can never be ok), and the 0.030 USDC per-call price. That is precisely the extra layer annotations cannot express: output shape, failure semantics, and cost.

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 definition is front-loaded with the use case, then the analytical scope, then the return contract, then the degradation case and price. It is dense but nearly every clause carries new information; the enumeration is long yet each item is a distinct capability rather than padding.

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 and only one input parameter, the description carries the burden of explaining what comes back, and it does: verdict plus reasons, section-level coverage on degraded runs, and cost. An agent can decide, call, and interpret the result without further context.

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?

The tool takes a single required parameter whose schema description coverage is 100% and whose pattern already constrains it to a base58 mint address. The description adds no format, network, or edge-case detail beyond the schema, so the baseline 3 applies.

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 names a specific resource (a Solana token's holder graph and mint history) and enumerates the concrete analyses: shared-funder clusters, post-merge concentration, snapshot dynamics, blacklist proximity, and mint authorities/Token-2022 extensions. Its purpose is unambiguous, though it never explicitly distinguishes itself from siblings like token_holders_delta or wallet_check, leaving that routing to inference.

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?

"Use before buying or holding a Solana token" gives a clear triggering context, which is exactly the decision an agent needs to place this call. It stops short of explicit when-not guidance or naming the alternative to use for lighter-weight holder queries, so it is strong but not exhaustive.

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