koios_genesis

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It only says 'Get the genesis parameters', which implies a read operation but does not mention pagination behavior, default limits, ordering, or response format. The agent is left without critical context for a safe and correct invocation.

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 concise sentence that efficiently conveys the core purpose. It is not overly verbose and earns its place, though it lacks any structural breakdown or additional context. The terseness is acceptable given the simplicity of the described action.

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 has no output schema, no annotations, and a one-sentence description. It does not describe what the response contains, how to paginate results, or why it differs from other parameter-related tools. For a blockchain data tool, this is insufficient to guide correct usage, especially without output schema or behavioral details.

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 provides complete descriptions for all four parameters (limit, order, offset, select), with 100% schema description coverage. The tool description adds no parameter-level semantics beyond the schema, but since the schema already does the heavy lifting, 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 clearly uses the verb 'Get' and specifies the resource as 'genesis parameters of the Cardano blockchain', making the purpose evident. It distinguishes from related siblings like koios_param_updates and koios_era_summaries by focusing specifically on genesis parameters, though it does not explicitly contrast them.

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 on when to use this tool versus alternatives such as koios_param_updates or koios_cli_protocol_params. The description simply states the action without any context, exclusions, or comparison to similar parameter-related tools.

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