reboot_vm

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

Annotations provide safety hints (non-read-only, non-destructive, non-idempotent). The description adds the detail 'via ACPI' indicating a graceful mechanism, but does not elaborate on side effects like temporary downtime or prerequisites like VM running state.

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 extremely concise with two sentences that front-load the core action and critical requirement. No superfluous words, but could be slightly expanded for completeness.

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?

While the output schema reduces the need to describe return values, the description omits important context such as whether the VM must be running, that the operation is asynchronous, or any side effects. It is minimally adequate for a simple reboot 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?

Input schema covers both parameters with descriptions, achieving 100% coverage. The description adds no new parameter information, so baseline score applies as per guidelines.

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 action (reboot) and resource (VM) with the specific method (via ACPI). It distinguishes from siblings like start_vm, stop_vm, and shutdown_vm by indicating a restart operation.

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 a necessary condition (PROXMOX_RISK_LEVEL=lifecycle) but lacks guidance on when to use this tool versus alternatives like shutdown_vm or stop_vm. The usage context is implied but not explicitly contrasted with siblings.

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