vm_reboot

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

No annotations are provided, so the description fully discloses behavior: it is a write operation ('[WRITE][risk=medium]'), irreversible ('No undo'), and the prior power state is only captured for audit records. This is comprehensive and accurate.

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 succinct: a brief purpose line, a one-sentence note on irreversibility, and a bullet list of arguments. Every sentence is relevant and there is no fluff.

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 tool with four parameters and no output schema, the description covers all essential aspects: purpose, mode choice, risk, irreversibility, and parameter details. It is complete and self-contained.

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?

The input schema lacks descriptions (0% coverage), but the description explains each parameter: vm_id source, force versus clean reboot, dry_run preview, and target default. The explanations are concise and add value beyond the parameter names.

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 a VM') and the resource (VM). It distinguishes two modes (clean vs hard) and explicitly mentions the verb 'reboot', which differentiates it from sibling tools like vm_start, vm_stop, and vm_migrate.

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 includes important context: 'No undo' and the irreversibility of the operation. It also explains the purpose of each parameter. However, it does not explicitly compare this tool to alternatives like vm_stop+vm_start, which would help an agent decide when to use reboot instead.

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