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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds practical behavioral context: pricing per call, x402 on Base, prepaid header option, free daily call, and no wallet/API key requirement. It also discloses the analysis dimensions (creator/owner holdings, infrastructure vs. unlabelled wallets, largest non-infra wallet), which goes beyond the annotations.

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 core purpose is front-loaded and the analytical categories are listed efficiently. Some promotional phrasing ('the analysis others skip') and pricing/access details extend the length, but they are relevant for invocation. Overall it is compact enough for the information it communicates.

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?

Given a single required parameter, an output schema, and safety annotations, the description covers the key invocation details: purpose, required input, cost, network, auth model, and analytical outputs. It is slightly less complete on when-to-use vs. sibling tools, but that gap is minor for a one-parameter read-only analysis.

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%: the only parameter, 'address', is already described as a token contract address. The description merely repeats 'Required input: address' and does not add details about expected format, validation, or examples beyond the schema.

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 states the tool classifies the holder base of a token and separates benign concentration (LP/CEX/bridge) from dangerous unlabelled wallets, with a specific verb 'classify' and resource 'holder base'. It does not explicitly name a sibling alternative, but it does distinguish itself from a naive 'top-10 = X%' analysis, which suggests differentiation from simpler holder tools like 'holders'.

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 implies the tool is for when you need to analyze whether a token's holder concentration is dangerous, and the phrase 'analysis others skip' positions it as a deeper alternative. However, it does not explicitly state when to use it vs. alternatives such as holders, rug_score, or whale_flow, nor does it give exclusion criteria.

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