koios_pool_delegators

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says to 'get current delegators' and does not disclose pagination behavior, response shape, data freshness, or whether this is a read-only operation beyond the implicit 'get' verb. The word 'current' adds some nuance but not enough.

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 a single, front-loaded sentence: 'Get current delegators for a specific pool.' Every word is substantive and there is no extra verbosity, making it highly concise.

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?

The tool has 5 parameters, no output schema, and no annotations, yet the description provides only a one-line summary. It does not describe return values, pagination behavior, or how this compares to the sibling history/invalid delegators tools, leaving the description incomplete for an agent to understand what the tool returns.

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 is 3 even with no parameter details in the tool description. The description does not repeat or add to the parameter information beyond naming the pool as the scope, but the schema already documents _pool_bech32, limit, order, offset, and select.

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 uses the specific verb 'Get' with the resource 'current delegators' scoped to 'a specific pool.' The adjective 'current' distinguishes this from sibling tools like koios_pool_delegators_history and koios_pool_invalid_delegators, satisfying the requirement for sibling differentiation.

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 context of retrieving current delegators is clear, and the word 'current' implies this is not for historical or invalid delegator queries. However, it provides no explicit guidance about when to choose this tool over the closely related koios_pool_delegators_history, koios_pool_invalid_delegators, or koios_drep_delegators.

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