pve_suspend_vm

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

No annotations are present, so the description carries the full behavioral burden. It only states 'Suspend' and the confirm requirement; it doesn't disclose reversibility, effects on running workloads, or what happens to the VM/container state. For a state-changing tool, this is a significant gap.

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 a single front-loaded sentence with no filler; every word carries meaning. It is concise but brief to the point of omitting useful context.

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 no annotations and zero schema parameter descriptions, the description is too thin for a mutating tool. It covers the critical confirm requirement and identifies the target, but omits behavioral effects and doesn't clarify vm_type. The output schema helps with 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 description coverage is 0%, and the description only compensates for 'confirm' by stating it must be true and hints that vm_type may distinguish VM vs container. node and vmid are left entirely to their names, and vm_type's accepted values are not explained.

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 uses the specific verb 'Suspend' and identifies the resource as a VM/container, which clearly distinguishes it from siblings like pve_start_vm, pve_stop_vm, and pve_resume_vm. It doesn't explicitly contrast with shutdown/stop, but the operation name and wording are unambiguous.

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?

No guidance is given on when to choose suspend over stop, shutdown, reboot, or resume. 'Requires confirm=true' is a call requirement rather than usage guidance, so an agent receives little help deciding between this tool and its alternatives.

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