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

With no annotations, the description carries the full burden of behavioral disclosure, and it only names the data source. It omits sort direction (top ascending or descending), default limit behavior when limit is unset, and any pagination or rate-limit context for what is clearly a ranked-read tool.

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?

A single front-loaded sentence with no filler, and the resource scope leads. It is efficient, though the brevity is part of why so little behavioral context is present.

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?

For a simple read getter with 100% param coverage and no output schema, the description is minimally adequate: it identifies resource, scope, and source. It is missing default-limit and ordering-direction behavior that an agent needs to call it correctly the first time.

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 both parameters (limit, order_by enum) are already documented in the schema. The description adds no syntax, default, or range detail beyond that, so the baseline 3 applies.

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 (get) and resource (top holders), plus the twin scopes (stLINK or reSDL) and the data source (LinkPool subgraph). It is clear, but it does not distinguish itself from sibling holder tools such as sdl_get_nop_holdings, sdl_get_staking_channel_holders, or sdl_get_resdl_positions, so the agent must infer the difference itself.

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?

No when-to-use guidance, no exclusions, and no named alternatives among a crowded set of holder-oriented siblings. The agent gets no signal on whether this is the right tool versus sdl_get_resdl_positions or sdl_get_staking_channel_holders.

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