Create Hard Fork Initiation Action

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is low, but the description adds nothing behavioral beyond a restated arg list. It does not mention that this likely builds an unsigned action requiring signing/submission, nor how the optional prev_governance_action_* fields chain actions, nor anything about the deposit lifecycle.

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 tight and front-loaded, but the nine-line Args block is fully redundant with a schema that already has 100% coverage, adding length without adding information.

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 9-parameter, 7-required governance-action constructor with no output schema, the description omits the transaction lifecycle (signing, submission), the role of the optional prev-action chaining inputs, and the deposit/return_addr flow that dominates the required parameters. An agent has the field list but not enough to use the tool correctly in context.

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 every parameter, and the description merely repeats those identical one-line descriptions verbatim. No extra meaning (formats, constraints, the significance of the optional prev-action pair) is added. Baseline 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: 'Create a hard fork initiation governance action.' An agent knows exactly what it produces. However, it offers no differentiation from the many sibling create-* governance actions (info, no_confidence, constitution, protocol_params_update, update_committee, treasury_withdrawal) beyond the tool name itself.

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 gives no guidance on when to use this action versus other governance action constructors, no prerequisites (e.g. a registered DRep/SPO/stake key, sufficient deposit), and no note about what happens after creation. Usage is left entirely to inference from the name.

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