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. It explains the effect of purge and destroy_unreferenced_disks parameters, adding transparency. However, it does not explicitly state that deletion is irreversible or describe the full scope of what is removed (e.g., VM config, disks).

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 extremely concise, starting with the main action and then listing parameters with short, clear explanations. No unnecessary words; every sentence contributes value.

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 essential action, precondition, and parameter behaviors. An output schema exists (though not detailed), so return values are covered. It lacks mention of default disk handling (beyond unreferenced) and irreversibility, but overall is adequate for an agent to use the tool correctly.

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?

The input schema has 0% description coverage, but the function description lists each parameter with a brief explanation. For 'purge' and 'destroy_unreferenced_disks', it provides specific effects beyond the parameter names. For 'node' and 'vmid', it gives minimal but adequate clarification.

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 'Delete a VM', specifying the verb and resource. It also includes a critical precondition ('The VM must be stopped first'), which helps distinguish this tool from other delete operations among siblings (e.g., delete_container).

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 a clear precondition (VM must be stopped) that guides when to use the tool. It does not explicitly list alternatives or when not to use it, but the resource name and context signals (sibling tools) are sufficient for differentiation.

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