koios_pool_delegators_history

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states the basic action without mentioning pagination behavior (limit/offset), epoch filtering, rate limits, or any side effects. While 'Get' implies a read operation, the description provides minimal behavioral context beyond the literal action.

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, well-formed sentence with no unnecessary words. It front-loads the core purpose clearly.

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 absence of annotations and output schema, the description is too sparse to provide adequate context. It does not explain what 'historical' means (e.g., delegators at a specific epoch vs. all historical changes), how pagination works, or how this tool relates to 'koios_pool_delegators'.

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%, with all 6 parameters having descriptions. The description itself adds no parameter-specific information, so it meets the baseline of 3. It does not clarify the meaning of 'historical' in relation to the epoch parameter or how limit/offset interact.

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 with a specific verb ('Get') and resource ('historical delegators for a specific pool'). The word 'historical' distinguishes it from the sibling tool 'koios_pool_delegators', which likely returns current delegators.

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 implies use for historical delegator data but does not explicitly state when to use it over alternatives. The sibling tool 'koios_pool_delegators' suggests a current-delegators counterpart, but the description does not mention this distinction or any exclusions.

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