pve_backup_delete

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

Discloses mutation, irreversibility, dry-run safety gate, async behavior (may return task UPID or null), and PLAN reporting. With no annotations, the description fully compensates.

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?

Compact and front-loaded with 'MUTATION:' label. Each sentence adds distinct value without fluff, covering behavior, safety, and recommendations efficiently.

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?

Addresses purpose, behavior, safety, async, and recommends sibling tool. Output schema exists, so return format detail is not required. The description is thorough for the tool's complexity.

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 100%, so baseline is 3. Description adds extra meaning for 'confirm' parameter (dry-run vs execute) and clarifies the 'volid' role via reference to pve_backup_list, raising it above baseline.

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?

Starts with 'MUTATION: delete a backup archive (removes a recovery point)' which clearly states the verb and resource. Distinguishes from sibling pve_backup_list by advising to check the archive list first.

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?

Explicitly explains dry-run default and confirm=True to execute. Advises to check pve_backup_list first and warns about irreversibility, providing clear when-to-use and prerequisite guidance.

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