pve_create_snapshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal that confirm=true is required, which is a useful API guard, but it does not explain what happens if confirm is omitted, whether the VM/container is paused, or what other side effects snapshot creation may have. For a mutating tool, this is incomplete.

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 two terse, front-loaded sentences with no filler. The action and the critical confirmation requirement are both stated directly, and every word earns its place.

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?

Despite having an output schema, this tool has seven parameters, no parameter descriptions, and no annotations. The description covers only the core action and the confirm gate, leaving an agent without guidance on targeting an LXC container via vm_type, what vmstate controls, or how to handle the confirmation requirement beyond setting it true. This is insufficient for a mutating operation.

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 needed to compensate by explaining the parameters. It only addresses confirm=true; node, vmid, snapname, vm_type, vmstate, and description receive no semantic guidance. Some names are self-explanatory, but vm_type's allowed values and vmstate's effect are left unspecified.

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 opens with a specific verb ('Create') and resource ('VM/container snapshot'), so an agent can immediately identify this as the snapshot-creation operation. This also distinguishes it from sibling tools like pve_delete_snapshot and pve_rollback_snapshot.

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 states a hard prerequisite (confirm=true) but gives no guidance on when to use this tool versus alternatives such as pve_delete_snapshot or pve_rollback_snapshot. There are no conditions, exclusions, or context about when snapshotting is appropriate.

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