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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds genuinely new behavior: data covers the top 1000 wallets and refreshes every 3 hours, plus it scopes the response ('calls only this endpoint and returns that response'). Freshness cadence is the kind of trait annotations cannot express.

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?

Front-loaded and short: the endpoint scope, subject matter, and returned fields come in order. The leading 'Top Holders.' restates the title and 'returns that response' is slightly circular, but there is no filler beyond that.

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 a full output schema and 100% parameter coverage, the description only needs to add orientation and cost/freshness context, which it does (top 1000 wallets, 3-hour refresh, endpoint isolation). Only the missing sibling routing keeps it from being fully 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%, with page, limit, sortByAsc/sortByDesc and mintAddress all documented in the schema, so the baseline is 3. The description's 'top 1000 wallets' loosely echoes the limit default but adds no sorting, pagination, or format guidance 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?

States a specific verb and resource ('fetching top token holders and whales') and names the exact endpoint, so an agent can tell it retrieves holder/distribution data rather than trades or counts. It stops short of explicitly contrasting with the nearest siblings (list-top-traders, get-token-holder-count-history, get-token-top-pnl-traders), leaving that differentiation 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?

Usage is implied by the endpoint description and the field list ('ownership %, USD value, and labels'), but there is no explicit when-to-use or when-not-to-use statement and no mention of the alternatives available in the sibling set. An agent must infer from names alone whether to pick this or list-top-traders.

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