pve_backup

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

With no annotations, the description discloses that it is a mutation, async, and can halt the guest in stop mode, but lacks details on permissions, idempotency, or side effects beyond what is stated.

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 highly concise with two efficient sentences, front-loaded with the purpose, and uses clear formatting for mode options without unnecessary 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 the return value (task UPID) and mode behavior, but omits prerequisites, error handling, or duration expectations, which are moderately important for a mutation tool with no annotations.

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?

Given low schema description coverage (13%), the description adds meaning to key parameters like mode and confirm, but fails to explain vmid, storage, compress, node, or kind, leaving gaps for the agent.

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 it performs backups using vzdump, specifies the mutation nature, and differentiates from sibling tools like pve_backup_list by focusing on the backup action and modes.

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 dry-run vs execute (via confirm) and lists modes, but does not explicitly guide when to use this tool versus alternatives like pve_backup_job_create or pve_snapshot_create, nor does it provide exclusion conditions.

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