Reboot Guest

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

With destructiveHint=true already set, the description adds the requirement of elevated permissions but does not elaborate on the disruptive nature of a reboot (e.g., temporary downtime or data loss for unsaved state). No contradiction exists; the description adds minimal context beyond the annotation.

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?

A single, compact sentence that front-loads the action verb and enumerates both supported resource types. No filler words; every element earns its place, making it easy to scan and understand quickly.

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 three-parameter reboot tool, the description covers the essential usage context: resource types and the permission prerequisite. No output schema exists, so return-value details are unnecessary. It could note preconditions like the guest being running, but this is likely implicit and not a significant gap.

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 schema covers node and vmid with descriptions but leaves type undocumented; the description compensates by explicitly mapping type=vm to VM and type=lxc to LXC container. This adds meaningful semantics beyond the schema, especially given 67% schema coverage.

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 states the specific action 'Reboot' and explicitly lists the resource types (VM and LXC container). This clearly differentiates it from sibling tools like start, stop, shutdown, and delete, leaving no ambiguity about the tool's purpose.

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 implies usage through its name and action but does not explicitly compare it to alternatives like shutdown+start or stop. No when-to-use or when-not-to-use guidance is provided beyond the note about elevated permissions, so the agent must infer the right context from the tool name.

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