pve_reboot_vm

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

With no annotations, the description carries the behavioral burden. It does disclose that confirmation is mandatory, which is a useful safeguard for a mutating operation. But it does not describe side effects, failure modes, or behavior when confirm is omitted, and it does not clarify whether the reboot is asynchronous.

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 short, front-loads the action, and has no filler. The confirm requirement is isolated as its own sentence, making it prominent. It is appropriately concise, though the terseness contributes to some under-specification.

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?

The output schema covers return values, and the core reboot action is clear. However, for a mutating tool amid many VM lifecycle siblings, the description lacks selection guidance, parameter semantics, and side-effect context. It is minimally viable but not fully complete.

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 explain the parameters. It only addresses confirm=true. node and vmid are somewhat inferable from their names, but vm_type is left unexplained, and there is no guidance on valid values such as qemu vs lxc.

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 ('Reboot') and a clear resource ('VM/container'), which is distinct from sibling operations like start, stop, shutdown, suspend, or resume. An agent can immediately identify the tool's job from the description alone.

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 provides one explicit operational prerequisite: 'Requires confirm=true.' However, it does not explain when to choose reboot over related tools such as start_vm, shutdown_vm, or stop_vm. Usage context is mostly implied by the word 'Reboot' rather than stated.

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