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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reasonably discloses the paid nature of the call, the exact cost, the payment rail (x402), and the network (Solana mainnet). It does not mention data freshness, whether the result is cached, or failure behavior, but for a simple read-only token data look-up the disclosed cost and network context are strong additions.

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 two sentences with no filler. The first sentence states the tool's action and outputs, the second provides the key differentiation from a sibling and the cost implication. All information earns its place and is front-loaded.

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?

The description covers the tool's purpose, output highlights, relation to get_token_risk, and cost, which is substantial given only one parameter and no output schema. The main gap is that it does not specify exactly how many accounts are returned or whether there is pagination/limiting. This is minor for a holder-lookup tool, so the definition is nearly complete.

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% and the single parameter 'mint' is already fully documented as an SPL token mint address in base58. The description adds only the broad 'any SPL token' claim and the output focus, which does not materially deepen the semantic understanding of the parameter. This matches the baseline for fully schema-documented parameters.

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 identifies the resource (SPL tokens) and the specific action (get top holders), and specifies the output dimensions: per-account share and top1/top5/top10 concentration. It also differentiates itself from the sibling get_token_risk by positioning this as the deeper holder-level cut. This gives an agent a precise, non-ambiguous purpose.

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 phrase 'Deeper cut than get_token_risk's summary' provides a direct comparison to a sibling tool and implies when this tool is preferable: when holder-level detail beyond a summary is needed. It does not explicitly state when not to use it or list exclusions, but the context is clear enough for correct selection among the many get_* siblings.

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