Issue Node Operational Certificate

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false, so the safety/immutability profile is partly covered. The description adds nothing operational: it doesn't say that the op cert counter file is consumed/incremented, that out_file is written or overwritten, or that kes_period must match the current chain period. For a mutating, non-idempotent key-material tool this is thin.

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 opening sentence is well front-loaded, but the trailing Args list duplicates the input schema one-for-one and occupies the majority of the text without adding information, which is padding rather than earned content.

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?

All five required parameters are named and there is no output schema, so return values need not be explained. Still missing for a five-required-param key-material tool: operational prerequisites, counter-file semantics, and any note on KES period validity — leaving the invocation context only minimally complete.

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 schema already documents all five parameters; baseline is 3. The description's Args block merely restates those same parameter descriptions verbatim (e.g., 'Path to KES verification key file'), adding no format hints, mutual constraints, or file-existence expectations.

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 first line states a specific verb+resource ('Issue an operational certificate') plus a scoping phrase ('for a block-producing node'), which is clear on its own. However, the sibling tool cardano_stake_pool_issue_op_cert exists and the description makes no attempt to distinguish the node-level path from the stake-pool path, so an agent cannot disambiguate from the text alone.

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 prerequisite chain (node key gen, KES/VRF key gen, counter init must precede this), and no statement of when to prefer this over cardano_stake_pool_issue_op_cert. The agent is left to infer all workflow ordering.

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