delete_snapshot_vm

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

With no annotations provided, the description carries the burden of warning about destructive behavior. It explicitly labels the operation as 'DESTRUCTIVE' and states the confirm=True requirement, adding critical safety context beyond what the schema shows (default false). However, it does not elaborate on irreversibility or other side effects.

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 a single, focused sentence that leads with the primary purpose and includes a crucial warning. There is no redundancy or irrelevant detail, making it efficient and front-loaded.

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 simple deletion tool, the description conveys the essential destructive nature and confirmation requirement, but it lacks any information about return values, expected response, or post-conditions. With no output schema and no annotations, a more complete description would help, but the core usage is adequately captured.

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 must compensate, but it only mentions the confirm parameter. The required parameters (node, vmid, snapname) are not explained, though their names are self-explanatory. This leaves the agent to infer their meaning and format without any descriptive support.

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 ('Delete') and the specific resource ('virtual machine snapshot'), distinguishing it from sibling tools like delete_vm (whole VM) and delete_snapshot_container (container snapshot). It is specific and unambiguous.

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 implies usage by naming the operation, but it does not explicitly discuss when to choose this tool over alternatives (e.g., rollback_snapshot_vm) or provide exclusions. The confirm=True requirement is the only contextual guidance.

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