reboot_vm

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

With no annotations, the description must fully disclose behavioral traits. It mentions ACPI (graceful reboot) but does not explain whether the operation is asynchronous, if a response confirms completion, or what happens if the VM is already powered off. Important safety details are missing.

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 concise, with the main action in the first sentence and parameters listed compactly. No unnecessary text, but the brevity sacrifices completeness. It earns a 4 for being well-structured and front-loaded.

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?

Given that this is a mutative VM operation with no annotations and an output schema (whose contents are unexplained), the description is too sparse. It omits prerequisites (VM must be running?), effects, and return value context. An agent would need external knowledge to use this tool correctly.

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 coverage is 0%, so the description bears full responsibility for parameter clarity. The description only restates parameter names and adds trivial explanations ('The node name', 'Wait timeout in seconds'). It does not explain semantics like what timeout=0 means, valid ranges, or how timeout affects behavior.

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'), and specifies the method ('via ACPI'), which gives a clear purpose. However, it does not differentiate from sibling tools like 'reset_vm' or 'shutdown_vm', which could lead to confusion about which tool to use for graceful vs. forceful restarts.

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 this tool versus alternatives (e.g., reset_vm for unresponsive VMs). The description implies a graceful reboot but doesn't state prerequisites or contraindications, leaving the agent without clear decision-making support.

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