Generate Node Cold Keys

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

Annotations already declare this is a non-read-only, non-idempotent write (readOnlyHint=false, idempotentHint=false), and the description's file-output paths reinforce that it writes to disk. However, it does not say whether existing files at those paths are overwritten or fail, which is the key behavioral risk for a non-idempotent key generator.

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?

Short and front-loaded with the action sentence first, which is the important part. The parameter listing is pure duplication of the schema, but it costs little space.

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 three-required-parameter key generator with no output schema, the description covers what is generated and where it lands, and annotations cover the write profile. It is still missing overwrite behavior and any hint about the sequencing with cardano_node_issue_op_cert, which is the natural next step.

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 Args block merely repeats the schema's own descriptions verbatim and adds no format, path convention, or overwrite semantics beyond what the schema already states.

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?

States a specific verb and resource: generates a node cold key pair plus an op cert counter. It is clear what is produced, but it does not distinguish itself from close siblings like cardano_node_key_gen_kes, cardano_node_key_gen_vrf, or cardano_node_new_counter, so an agent must infer which key-generation variant applies.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives, despite a crowded sibling set of key-gen tools. The agent gets no help deciding between cold, KES, VRF, and counter operations.

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