pve_resume_vm

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

With no annotations, the description must carry behavioral disclosure. It does surface the non-obvious requirement that confirm must be true, which is useful. However, it omits state prerequisites and what happens when confirm is false or when the VM is not suspended.

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 sentences, front-loaded with the action and a key requirement. There is no filler or redundant content; 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?

For a mutating tool with no annotations and no schema descriptions, this is too sparse. It lacks the suspended-state precondition, vm_type guidance, and explicit differentiation from related start/reboot tools. The presence of an output schema covers return values but not invocation semantics.

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 property descriptions have 0% coverage, and the description only compensates for the confirm parameter. Node and vmid are inferable by name, but vm_type with default 'qemu' is unexplained, and no parameter semantics beyond confirm=true are provided.

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 the verb 'Resume' and the resource 'VM/container', making the core operation identifiable. However, it does not explicitly distinguish this tool from sibling start/suspend/reboot tools or mention the 'suspended' precondition, so differentiation is mostly left to inference.

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?

There is no guidance about when to use this tool versus alternatives. It does not say it applies to previously suspended VMs/containers, nor does it point to pve_start_vm for stopped VMs. 'Requires confirm=true' is a call requirement, not usage guidance.

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