Create Vote Delegation Certificate

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety/mutation profile is covered by structured data. The description adds only that a certificate file is written to out_file, with no mention of permissions, overwrite behavior, or what the cert is meant to feed into. Adequate but not rich beyond the annotations.

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 lead sentence is well front-loaded and the closing constraint sentence earns its place. But the bulleted Args list just restates the schema's property descriptions verbatim at 100% coverage, adding bulk without information — a waste that keeps this from scoring higher.

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 certificate-generation tool with no output schema, the definition explains inputs and the exclusivity rule but says nothing about the produced certificate's format, where it plugs in (transaction assembly/signing), or that it is an intermediate artifact rather than a submitted operation. An agent gets enough to call it, but not enough to place it in a workflow.

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 already 100%, so parameter meanings are fully documented structurally. The description does add value beyond the schema by stating the mutual-exclusivity constraint among the three delegation targets, which the schema's additionalProperties/required fields do not express. It stops short of clarifying interaction between always_abstain and always_no_confidence flags.

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 vote delegation certificate') and clarifies the three delegation targets (DRep, always-abstain, always-no-confidence). It distinguishes itself from the many query/certificate siblings by the 'vote delegation' qualifier, though it never explicitly contrasts itself with the closely named cardano_stake_address_delegation_certificate (stake vs vote).

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 supplies the key selection rule among the three target modes ('Exactly one of drep_verification_key_file, always_abstain, or always_no_confidence must be provided'), which is genuine usage guidance. However it gives no when-to-use vs. alternatives context, no prerequisites, and no indication of when a vote delegation cert is appropriate versus the sibling certificate tools.

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