vm_reboot

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

Discloses the operation is a write ('[WRITE]') and 'graceful', but with no annotations, fails to detail permission requirements, whether the reboot is synchronous or asynchronous, or any side effects on VM state beyond reboot.

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 concise paragraphs with no fluff. Front-loaded with purpose and key behavioral note. Parameter list is minimal and clear.

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 simple reboot operation with 3 simple parameters and no output schema, the description covers the main points. Omits details like 'graceful' semantics, idempotency, or cooldown, but these are minor for a typical reboot.

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?

Without schema descriptions (0% coverage), the description explains all three parameters: vmid (numeric id), target (Proxmox target name from config), and node (optional, auto-locate if omitted). This adds crucial meaning beyond types.

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?

Clearly states 'Reboot a VM (graceful)' with a specific verb and resource. The '[WRITE]' prefix adds context. Distinguishes from sibling tools like vm_shutdown and vm_stop by implying a restart (not stop or shutdown).

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?

Explicitly notes 'No undo token — reboot has no inverse', warning agents about irreversibility. However, does not explicitly compare to alternatives like vm_shutdown or vm_stop for when a reboot is preferred over a shutdown/start sequence.

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