koios_tx_outs_epoch

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 claims to return 'all' outputs but does not mention pagination (limit/offset), ordering, or that results may be limited, which is a significant omission. It also does not clarify whether this is a read-only operation or what the response shape looks like.

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 with no filler or repetition. Every word contributes to conveying the core function, making it highly concise and easy to parse.

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 has five parameters, no output schema, and no annotations, the description is too sparse. It does not explain how pagination works, what fields are returned, how 'all' interacts with limit/offset, or any rate-limit or permission context. This is a complex query tool, and the minimal description leaves the agent under-informed.

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 description coverage is 100%, so all five parameters have descriptions in the schema itself. The tool description adds no parameter-specific meaning beyond the schema, but it does not need to because the schema is already self-documenting. Baseline score 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 uses a specific verb ('Get') and resource ('transaction outputs') with a clear scope ('for a specific epoch'), making its purpose unambiguous. It distinguishes itself from sibling tools like koios_tx_info or koios_address_outputs by focusing on all transaction outputs at the epoch level, so the agent can select it appropriately.

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 guidance is provided about when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or comparisons with siblings such as koios_tx_info, koios_address_outputs, or koios_utxo_info. The description implies its use case but offers no explicit direction.

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