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

Annotations already declare the safe read-only, idempotent, open-world profile. The description adds valuable behavioral context beyond that: it names the exact JSON-RPC methods used and discloses that most endpoints return up to 20 holders while some nodes allow up to 100. It does not discuss authentication or rate limits, but the data-source and result-cap transparency is a meaningful addition.

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 text is front-loaded with the core purpose and packs return details, use cases, and data provenance into three efficient sentences. Every sentence contributes useful information with no filler. The structure moves cleanly from what it returns, to when to use it, to how it is sourced and limited.

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?

There is no output schema, so the description carries the burden of describing return values, which it does thoroughly: owner wallet, token-account address, raw and decimal balance, percentage of total supply, total supply, decimals, and combined top-holder share. Combined with annotations covering safety and the schema covering inputs, an agent has everything needed to call and interpret the tool correctly.

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 input schema already documents both the mint address format and the limit range. The description only indirectly touches the limit parameter by mentioning endpoint-dependent holder caps, without adding syntax or default details beyond the schema. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 states a specific verb and resource: "Top holders of a Solana SPL token by mint address." It distinguishes itself from sibling tools like solana_wallet_tokens by focusing on a token's largest accounts rather than a wallet's holdings. An agent can identify exactly what the tool retrieves without opening the 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?

The description gives clear context by naming the user questions it answers: "who are the biggest holders of this Solana token" and "how concentrated is its supply." It does not explicitly compare itself to alternatives or state when not to use it, but the intended scenario is unambiguous. No exclusions or prerequisite guidance are provided, so it falls short of a 5.

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