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

With no annotations, the description carries the full disclosure burden; it does well to state the paid cost ($0.005 USDC per call) and to describe what is returned, which a raw schema would not reveal. However, it says nothing about read-only/safe semantics, whether 'full' truly means all holders or is capped by `limit`, or pagination behavior, so it is helpful but incomplete.

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?

Three short sentences, front-loaded with the core purpose, then the return shape, then the cost. No sentence is redundant.

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?

For a two-parameter read tool with no output schema, the description sufficiently explains purpose, return contents, and pricing. It would be complete at 5 if it clarified how `limit` interacts with 'full' holder list and how it differs from holder_changes.

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%, so both `mintAddress` (base58) and `limit` (default 25) are already fully documented. The description amplifies the return fields rather than adding syntax or edge-case guidance for the parameters, 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 definition opens with a specific verb and resource ('Get full holder list for a Solana token') and enumerates the return payload (top holders, balances, % of supply, distribution metrics), so the agent knows exactly what it does. It does not explicitly distinguish itself from the close sibling holder_changes, which is the main gap keeping this at a 4.

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 'with concentration analysis' hints at a use case but never states when to choose this over holder_changes, token_risk_score, or top_traders, nor any exclusions or prerequisites. Like the MID calibration example, this leaves the agent to infer the decision rule.

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