pve_backup_delete

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

The description explicitly states the mutation nature, dry-run default, and async behavior including possible return values. It lacks disclosure of permissions or storage constraints but is fairly transparent given no 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?

Highly concise with two sentences. The first sentence states purpose, the second adds critical behavioral details. No wasted words.

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?

The description covers key behavioral aspects (mutation, dry-run, async) but lacks parameter guidance and prerequisites. Given an output schema exists, return values are partially handled, but required inputs are not explained.

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 only 20%, so the description must compensate. It explains the confirm parameter's role but does not describe required parameters like storage and volid, or optional node. This leaves agents without sufficient guidance on specifying the backup.

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 the action ('delete a backup archive') and the resource ('recovery point'). It distinguishes from sibling tools like pve_backup (create), pve_backup_list (list), and pve_restore (restore).

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 provides behavioral context (dry-run default, async) but does not explicitly state when to use this tool versus alternatives or when not to use it. No direct guidance on prerequisites or exclusions.

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