vm_delete

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

Without annotations, the description fully carries the burden: declares high risk, destructive behavior, dry-run safety, and audit trail capture of prior name/power state. All key behavioral traits are disclosed.

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, uses a clear header with risk tagging and an organized Args section. Every sentence adds value 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?

Covers purpose, safety, parameters, and audit behavior well. Lacks explicit details on return values (though dry_run behavior is described) and error handling, but for a delete tool this is mostly adequate.

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 detailed explanations for all three parameters (vm_ext_id, dry_run, target), compensating for the 0% schema coverage. Each parameter's purpose and origin are clearly stated.

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' with a specific verb and resource, and distinguishes it from other VM operations like power off or reboot among siblings. The destructive nature is highlighted upfront.

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?

Provides explicit guidance to use dry_run=True for preview before deletion, which is crucial for a destructive tool. However, it does not contrast with alternative VM actions (e.g., when to delete vs. power off), so it could be stronger.

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