pve_ha_rule_delete

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

With no annotations, the description carries full burden. It discloses dry-run, plan details (current rule, resource constraint loss, CRM migration), synchronous execution, and risk level. It doesn't mention permissions or error handling, but provides substantial behavioral context.

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 description is concise, front-loaded with 'MUTATION: delete an HA rule', and uses three sentences without wasted words. Every sentence adds essential 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?

Given that an output schema exists, the description covers purpose, behavior, dry-run, confirm, synchronous, and risk. It omits prerequisites and error scenarios but is sufficient for a deletion tool with good annotations 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 coverage is low (33%). The description adds value to the 'confirm' parameter by explaining its role in executing the action, but does not elaborate on 'rule' or 'proximo_target'. Partial compensation for coverage gap.

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 description clearly states 'MUTATION: delete an HA rule', using a specific verb and resource. It distinguishes itself from siblings like pve_ha_rule_create, pve_ha_rule_update, and pve_ha_rules_list by focusing on deletion.

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 explains the default dry-run behavior and how to execute with confirm=True. It's clear when to use this tool (to delete an HA rule), but lacks explicit when-not-to-use or prerequisites, which would improve it further.

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