koios_drep_list

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, but it only states the basic action. It does not mention that this is a read-only operation, that results are paginated via limit/offset, or what fields are returned. This is particularly insufficient given the lack of an output schema.

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 that immediately states the tool's purpose. It contains no fluff or repetition, making it an appropriately concise and well-structured description.

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 is a simple read-only list endpoint with four optional parameters, so the description's brevity is somewhat acceptable. However, the absence of an output schema and the lack of any indication of pagination or relationship to sibling DRep tools means the description is only minimally complete for an agent to fully understand what will be returned and how to choose this tool.

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. The description adds no additional meaning beyond what the schema already provides for limit, order, offset, and select. While some schema descriptions are thin (e.g., 'Column ordering'), the description itself does not compensate for or enrich these definitions.

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 verb 'Get' with the resource 'list of all registered DReps' and expands the acronym, clearly indicating the action and scope. It distinguishes from DRep-specific tools like koios_drep_info by emphasizing 'all', but it does not explicitly name any sibling alternatives, so it falls short of a 5.

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 provides no guidance on when to use this tool versus alternatives such as koios_drep_info, koios_drep_updates, or koios_drep_delegators. It also omits any mention of pagination behavior or intended use cases, leaving the agent without context for selection.

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