pve_delete_vm

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that deletion requires confirm=true, which is a key safety behavior. However, it does not disclose that this is a destructive, irreversible operation, what happens to associated resources (e.g., disks, snapshots) by default, or whether purge/destroy_unreferenced_disks affect those resources. The description is too terse to fully inform an agent of the consequences.

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 very short: one sentence plus a requirement. It is front-loaded with the action and the critical prerequisite. It earns its place, though it could add a bit more context without becoming bloated.

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 this is a destructive operation with 6 parameters, no annotations, and an output schema, the description is incomplete. It does not explain the destructive consequences, the meaning of optional parameters, or the difference between VM types. An agent could call it correctly with confirm=true, but might not understand the full impact of purge or destroy_unreferenced_disks, or that deletion is irreversible.

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 0%, so the description must compensate for the schema's lack of parameter explanations. The description only mentions 'confirm=true' and the resource type (VM/container), but does not explain the meaning of purge, destroy_unreferenced_disks, vm_type, or how node/vmid relate. The parameter names are somewhat self-explanatory, but the description adds minimal value beyond the schema.

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 states a clear verb and resource: 'Delete a VM/container.' This distinguishes it from sibling tools like pve_start_vm, pve_stop_vm, pve_create_snapshot, etc. It doesn't explicitly name a sibling alternative, but the action is unambiguous. The mention of 'Requires confirm=true' adds a necessary operational detail.

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 implies when to use this tool: when you want to delete a VM or container. It does not explicitly state when not to use it or mention alternatives (e.g., pve_shutdown_vm for graceful stop, pve_stop_vm for forced stop). The 'Requires confirm=true' is a usage prerequisite, which is helpful, but there is no guidance on choosing between VM types or when to use purge/destroy_unreferenced_disks.

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