get_token_holders

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

No annotations are provided, so the description carries the full burden. It discloses the data source (Blockscout index) and input flexibility (ticker or contract address), but does not explicitly mention safety profile, side effects, or error behavior. For a simple read-only query, this is adequate but not rich.

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 two sentences, immediately states what the tool returns, and avoids any filler. It is front-loaded and every sentence earns its place.

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 tool's low complexity (one parameter, no output schema), the description is nearly complete. It specifies the key outputs (holder count and top-10 concentration), data source, and input. It omits potential limitations or error cases, but for a simple query tool this is sufficient.

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?

The schema already provides 100% coverage of the single parameter 'token' with a clear description ('Ticker or ERC-20 contract address (0x...)'). The description reinforces this but adds no new meaning beyond what the schema offers, so the baseline of 3 is appropriate.

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's function: it returns holder count and top-10 holder concentration for an ERC-20 on Robinhood Chain. This specific verb-resource pairing distinguishes it from sibling tools like get_token_supply or get_token_market, which focus on different data aspects.

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 explicitly says to use it for analyzing how concentrated ownership of a tokenized asset is, which provides clear context. It does not name alternative tools or state when not to use it, but the intended use case is well implied.

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