Delete VM

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

The description adds the important behavioral note about requiring user confirmation and emphasizes permanence, going beyond the destructiveHint annotation. No contradiction with annotations is present.

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—two sentences with no fluff—and front-loads the key purpose and caution.

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 tool is destructive and has an output schema absent, the description adequately covers the core behavior and necessary caution. It could briefly mention the result or impact on related resources, but it's sufficient for a delete operation.

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 description provides no additional meaning for the parameters beyond the input schema. With schema coverage at 60%, it fails to compensate for undocumented parameters like node and vmid.

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 'permanently delete a VM and its disks' and highlights its destructive nature, distinguishing it from other delete operations like delete_container or delete_backup.

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 advises to ask the user for confirmation before invoking, providing clear usage context. However, it does not explicitly state when not to use the tool or mention alternatives among the many delete siblings.

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