koios_epoch_info

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds context by specifying the included fields (times, block counts, tx counts) and clearly implies a read-only operation. However, it does not disclose default behavior (e.g., which epoch is returned when _epoch_no is omitted) or pagination defaults, which are only implied by the 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, compact sentence that front-loads the action ('Get epoch-specific information') and specific content. Every phrase contributes value, with no redundancy or filler.

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-only info tool with a well-described schema, the description is largely sufficient. It lacks an output schema, so mentioning the likely return structure or default epoch selection would improve completeness, but the current text plus schema provide enough to understand basic usage.

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 provides full descriptions for all 6 parameters, achieving 100% coverage. The tool description adds no additional parameter semantics beyond what the schema already documents, so the baseline 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' with a clear resource 'epoch-specific information' and enumerates three key data fields (start/end times, block counts, transaction counts). This distinguishes it from sibling epoch-related tools like koios_epoch_params or koios_epoch_block_protocols, which have narrower focus areas.

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 compared to alternatives such as koios_epoch_params or koios_epoch_info. It does not mention any exclusions, prerequisites, or typical use cases, leaving the agent to infer usage from the tool name and field list.

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