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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description adds real operational context: data provenance (supply from NEAR RPC, holders from NearBlocks), the labelling logic that prevents pools/unissued stock being read as whales, and the cost/limit model ($0.02/call over x402 on Base, prepaid x-credit-token header, 1 free call/day). Error behaviour and pagination for large holder sets are not described, so it falls short of a 5.

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 with a scoping question and the core deliverable, then provenance, then payment terms. The middle sentence is a long run-on packing labelling, concentration tiers and sources together, but every clause earns its place and nothing 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?

An output schema exists, so return structure needn't be spelled out, yet the description still explains what comes back (holder count, shares, LOW/MEDIUM/HIGH concentration) and where the numbers originate. Provenance and pricing are covered; only the when-to-use routing against sibling holder tools is absent.

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% and both parameters are self-documenting ('token' = NEAR token contract account, 'top' = holders to list, 1-25). The description only restates that token is required and hints at holder count/shares, adding no default value or format detail beyond the schema. Baseline 3 applies when the schema carries the 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?

States a specific verb+resource: top holders of a NEP-141 token on NEAR, each with share of total supply, plus concentration of plain accounts. It also names the classification scheme (token/treasury/contract/plain account), which makes it distinguishable from generic siblings like holders, holder_forensics and token_supply.

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?

It states the required input and the payment model, and implies the use case ('how concentrated is it?'), but never says when to pick this over holder_forensics, holder_overlap, holders or token_supply. No exclusions or alternatives are named, so routing depends on the agent inferring from the NEAR/NEP-141 framing.

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