remove_snapshot

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description correctly aligns with annotations. The description adds meaningful extra context by specifying that the snapshot is deleted irrevocably and that the VM must be powered off, going beyond what the annotations alone reveal.

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 short, front-loads the destructive warning, and contains no filler. Every sentence earns its place: what it does, that it is irreversible, and when it is allowed.

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 three-parameter destructive tool with no output schema, the description covers the important precondition (VM powered off) and the irreversible nature of the operation, while the schema covers all parameters. It does not describe return values or error behavior, but that gap is minor given the annotations and complete schema.

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 100%, with the schema already documenting id, name, and confirm. The description adds no parameter-specific detail beyond the schema, so the baseline of 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 the action: deleting a snapshot, backed by the explicit vm/remove_snapshot identifier, so an agent knows what operation this tool performs. It does not explicitly contrast with sibling tools like restore_snapshot or create_snapshot, but the destructive delete framing is 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 provides a key operational prerequisite: deletion is possible only on a powered-off VM. It does not mention alternative snapshot operations or when not to use this tool, but the core usage condition is explicit and valuable.

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