pve_create_snapshot

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

Annotations already declare destructiveHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds the meaningful detail that a confirm=true flag is required, but says nothing about whether the snapshot is synchronous, how wait/timeout behave, or that snapshots consume storage — a notable gap for a 9-parameter mutation.

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 short, front-loaded sentences with no filler. It is efficient, though the terseness contributes to the documented gaps rather than balancing them.

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?

With 9 parameters, zero schema descriptions, and no output schema referenced in prose, the description is far too thin to call this tool correctly without reading the schema. The required-confirm note is the only behavioral aid provided.

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, and it only covers confirm. Nothing explains vmstate (memory capture), wait, timeout, kind (qemu vs lxc), node, or description, even though these materially change behavior.

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 a specific verb and resource ("Create a snapshot of a VM/container"), which is unambiguous. It does not explicitly distinguish itself from sibling operations like pve_rollback_snapshot or pve_delete_snapshot, so it stops short of a 5.

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?

It surfaces one important precondition ("Requires confirm=true"), which tells an agent it must set a flag before invoking. However, it offers no guidance on when to prefer this over pve_rollback_snapshot or how it relates to pve_list_snapshots, leaving selection largely to inference from the name.

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