snapshot_delete

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

Despite no annotations, the description labels the operation as [WRITE][risk=high], declares irreversibility, describes audit logging, and notes dry_run for safety.

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 sentences and a brief Args section; front-loaded with purpose and risk. No redundant information.

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, risks, parameters, and audit behavior. Lacks explicit return value description, but for a delete operation this is 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?

All three parameters (snapshot_id, dry_run, target) are explained beyond the schema, which has 0% coverage. Provides defaults and cross-reference to snapshot_list.

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 states 'Delete a VM snapshot by uuid' with a clear verb and resource, and includes risk labeling. It distinguishes from sibling tools like snapshot_list and snapshot_create.

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 context for when to use (deletion) and mentions dry_run for preview, but does not explicitly state when not to use or compare to alternatives like snapshot_revert.

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