delete_vm

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

With no annotations provided, the description fully covers behavioral traits: it labels the operation 'DESTRUCTIVE', states irreversibility, specifies what gets deleted (VM and disk images), and explains that confirm must be true to execute with preview behavior otherwise. This is thorough and sets clear expectations.

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 concise and front-loaded with 'DESTRUCTIVE', followed by two essential sentences and a clear argument list. Every sentence provides necessary information without redundancy.

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 the complexity of a destructive delete operation, the description covers all key aspects: purpose, irreversibility, prerequisite (VM stopped), parameter semantics, and preview behavior. Since an output schema exists, return values are not expected in the description.

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 compensates fully. It explains vm_id as 'The VM identifier' and confirm as 'Must be true to execute. Returns a preview otherwise.' This adds critical meaning beyond the schema's type and default, especially the safety-gate and preview behavior.

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 a specific action: 'Permanently delete a virtual machine and its disk images.' It distinguishes this from sibling tools like delete_disk or delete_snapshot by explicitly including disk images and emphasizing permanence.

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 clear context: the operation is destructive, cannot be undone, and requires the VM to be stopped first. It does not explicitly mention alternatives like shutdown_vm for non-destructive stopping, so it lacks explicit when-not-to-use guidance.

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