vm_delete

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

Full disclosure: marks as [WRITE], states permanent destruction, no undo token, mentions audit trail to ~/.proxmox-aiops/audit.db, and explains dry_run preview. Since no annotations provided, description carries full burden and meets it.

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?

Efficiently structured: summary line, critical warnings, usage instruction, then parameter list. No redundant text, all sentences earn their place.

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?

Covers all needed aspects for a destructive 4-parameter tool: what it does, safety warnings, preview option, audit logging, parameter roles. No gaps.

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?

Adds detailed meaning for all 4 parameters beyond the schema (which has 0% coverage): vmid is numeric ID, dry_run previews without destroying, target is from config, node can be auto-located.

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?

Clearly states 'Permanently destroy a VM' with explicit [WRITE] tag and 'IRREVERSIBLE' warning, distinguishing it from sibling tools like vm_start, vm_stop, vm_shutdown, etc.

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?

Explicitly instructs to 'Confirm with the user before calling' and suggests using dry_run=True to preview. Lacks explicit when-not-to-use or comparisons to alternatives, but context of irreversibility is clear.

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