pdm_pve_qemu_snapshot_create

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

With no annotations, the description carries full burden. It discloses that it is a mutation ('MUTATION'), is additive and low risk, and has a dry-run default. However, it omits important behaviors: how the 'confirm' parameter affects actual creation, prerequisites, or what happens on failure. The explanation of vmstate is a plus.

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 very concise with two sentences plus a tag, front-loading 'MUTATION' and the core action. Every word adds value, though the structure could be slightly improved by grouping behavioral notes.

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?

Given 7 parameters, no annotations, and low schema coverage, the description is too sparse. It lacks explanations for most parameters, does not mention error conditions or prerequisites, and relies heavily on the tool name and schema. While an output schema exists, the description still feels incomplete for a mutation 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%, so the description must compensate. It adds meaning for 'vmstate' (includes RAM state) and implies the dry-run behavior relates to 'confirm'. But it does not explain other key parameters like vmid, remote, snapname, or description, leaving them to schema names alone.

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 it snapshots a VM on a PDM-registered remote, specifying the resource (VM) and action (snapshot). It differentiates from sibling tools for delete/rollback and LXC snapshots, and from direct PVE snapshot tools by mentioning 'through PDM'.

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 context by stating 'on a PDM-registered remote (through PDM)', which guides the agent to use this for PDM-managed VMs as opposed to local PVE snapshots. However, it does not explicitly state when not to use it or mention alternatives among siblings, slightly reducing clarity.

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