pve_snapshot_delete

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

Discloses mutation, dry-run default, need for confirm=True, and async return of UPID. With no annotations, this is helpful, though lacks detail on side effects like snapshot removal from VM.

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 labels ('MUTATION:', 'Async -> UPID') for quick scanning; no unnecessary 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?

Covers key behavior but lacks details on optional parameters. Output schema exists, so return value explanation is adequate. Overall moderate completeness for a 7-param tool.

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 only 14%; description only implies 'snapname' and 'confirm', leaving 5 other parameters (vmid, force, kind, node) unexplained.

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?

Description clearly states the tool deletes a snapshot, specifies it's a mutation, and distinguishes it from sibling tools like pve_snapshot_create and pve_snapshot_list.

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 on dry-run and confirm flag, but lacks explicit guidance on when to use vs alternatives (e.g., pve_rollback) or prerequisites.

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