reboot_vm

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

With no annotations, the description must disclose behavior, but it only says 'Reboot a running QEMU virtual machine.' It does not state whether the reboot is graceful or forced, whether a confirmation parameter is required, what happens if the VM is not running, or any side effects like data loss. The presence of a 'confirm' boolean in the schema is not explained, and the description provides no additional behavioral context.

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 or redundancy. It clearly states the core action and resource, earning its place, though it is extremely terse and leaves out important detail (penalized in other dimensions).

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 VM reboot tool with no annotations, no output schema, and three parameters, this description is insufficiently complete. It does not explain the confirmation flag, the expected behavior for non-running VMs, or the result of the operation, so the agent cannot fully anticipate the tool's behavior.

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 does not mention or explain any of the three parameters (node, vmid, confirm). The description adds no meaning beyond the schema field names, leaving the agent without guidance on how to fill them correctly.

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 a specific verb 'Reboot' and identifies the resource 'QEMU virtual machine', clearly distinguishing it from sibling tools like stop_vm, start_vm, or shutdown_vm. It also specifies the condition 'running', which adds precision.

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 provided on when to use reboot_vm versus alternatives such as stop_vm and start_vm, shutdown_vm, or restart_container. The description lacks context like 'Use for restarting a VM without full stop/start' or prerequisites like the VM must have QEMU guest agent installed. No exclusions or alternative tools are mentioned.

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