get_epoch_info

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

With no annotations, the description carries the transparency burden. It discloses that the tool returns current epoch progress and lists the return fields, which is useful. However, it does not describe how the 'commitment' or 'min_context_slot' parameters affect behavior, nor any other behavioral details beyond the basic read operation.

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 is front-loaded with the core purpose. Every word adds value, and the list of return fields is densely informative without verbosity.

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?

There is no output schema, so the description must explain return values, and it does list the fields. However, it completely omits parameter semantics and does not clarify how commitment values work or what min_context_slot means. Given the lack of annotations and schema descriptions, the tool is under-specified for reliable invocation.

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 input schema has 0% description coverage, and the description does not mention the parameters commitment or min_context_slot at all. The agent must infer meaning solely from parameter names and defaults, which is insufficient for correct usage.

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 purpose with a specific verb ('Get') and resource ('current epoch progress') and lists the exact fields returned (absolute slot, block height, epoch, slot index/total). This is easily distinguishable from sibling tools like get_slot or get_health.

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 usage for retrieving epoch progress information but does not explicitly mention when to choose this tool over alternatives. No exclusion context is given, but the purpose is clear enough that an agent would know to use it when epoch-related data is needed.

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