Delete guest

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

With no annotations, the description carries full burden. It discloses the destructive, irreversible nature and the confirm guard. However, it does not mention the purge parameter's behavior (removal from backups/HA, default true) or other side effects. Partial coverage.

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?

Two concise sentences with key information front-loaded (permanent destruction) followed by the critical guard requirement. No wasted words.

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?

For a destructive tool without annotations or output schema, the description covers the essential aspects: what it does, the irreversible nature, and the confirmation mechanism. It lacks mention of the purge parameter's implications, but overall fairly complete.

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 coverage is 100% with descriptions for all three parameters. The description reinforces the confirm parameter requirement but adds no meaningful extra meaning beyond the schema. Baseline 3 is appropriate.

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 'PERMANENTLY destroy a VM or container and its disks. IRREVERSIBLE.' This provides a specific verb (destroy) and resource (VM/container and its disks), distinguishing it from siblings like backup_guest or clone_guest.

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 emphasizes that the action is permanent and irreversible and notes the confirm parameter requirement, but does not explicitly contrast with alternatives (e.g., shutdown vs. delete) or provide when-not-to-use guidance. Usage is implied rather than explicit.

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