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

Annotations already mark the tool readOnly, idempotent, and non-destructive. The description adds meaningful context beyond that: supply comes from the NEAR RPC, holders from NearBlocks, outputs are classified by holder type, and call pricing/auth requirements are disclosed. No contradiction with 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 description is front-loaded with the core purpose, then efficiently covers outputs, data sources, required input, and pricing. The pricing and free-tier detail adds length but is operationally useful, so the structure remains effective.

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 the output schema and annotations, the description covers all call-critical context: purpose, output contents, holder classification logic, data provenance, required input, cost, auth header, and the lack of wallet/API key requirement. Nothing essential is missing.

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 baseline of 3 applies. The description only restates that token is required and does not add deeper semantics beyond the schema's definitions of token and top.

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 opens with a precise use case—identifying who holds a NEAR NEP-141 token and measuring concentration—then enumerates specific outputs: top holders, share of total supply, holder labels, and concentration tiers. This clearly distinguishes it from generic holder or whale-tracking siblings.

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 tool is clearly scoped to NEP-141 tokens on NEAR and states the required token input, plus operational prerequisites such as the prepaid x-credit-token header and free tier. It does not explicitly name alternatives like holders or whale_flow, so it stops 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.