Issue Operational Certificate

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered externally. Beyond that, the description only restates the parameters; it never mentions that a file is written to out_file, whether an existing file is overwritten, or that the counter file is consumed/incremented. For a key-material/certificate operation that is a meaningful gap.

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 leading sentence is front-loaded and clear, but the five-line Args list duplicates a schema that is already 100% documented, so a sizable portion of the text does not earn its place. Structure is conventional rather than wasteful, but not lean.

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 5-required-parameter cryptographic issuance tool with no output schema, the description omits the operational context an agent needs: prerequisite artifacts, how kes_period is obtained, and what the tool returns or writes. It is barely more than a restatement of the schema.

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% and the Args block merely repeats the schema descriptions verbatim, adding no new semantics. Per the baseline rule for high coverage with no incremental parameter info, a 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?

States a specific verb and resource: 'Issue an operational certificate for a stake pool'. An agent knows exactly what is created. It does not, however, distinguish itself from the very similar sibling cardano_node_issue_op_cert, so the pool-vs-node distinction is left implicit.

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 mention of prerequisites (KES keys and counter file must already exist, KES period must correspond to the current epoch), and no routing to the sibling node-level op cert tool. The agent must infer the entire workflow context.

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