restart_vm

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

No annotations are provided, so the description must carry the full burden. It only states 'Restart a VM' without disclosing whether it is a graceful reboot, forced power cycle, or what happens to running processes. It also does not mention if the VM needs to be running or what the error behavior is.

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 short phrase with no wasted words, making it very concise. However, it is so minimal that it sacrifices useful context for brevity, which slightly reduces the score from a perfect 5.

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 mutation tool with no annotations and no output schema, the description fails to provide enough context about the operation's effects, prerequisites, or relationship to sibling tools. The schema covers parameters well, but the overall description is insufficient for confident tool selection.

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 100%, with both 'node' and 'vmid' clearly described in the input schema. The tool description adds no extra parameter information beyond what the schema provides, so the baseline score of 3 applies.

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 'Restart a VM' clearly states the action (restart) and resource (VM), distinguishing it from sibling tools like start_vm and stop_vm. However, it provides no additional context about what restarting entails, so it is clear but not highly informative.

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 given on when to use this tool versus alternatives like start_vm, stop_vm, shutdown_vm, or restart_container. The description does not mention prerequisites (e.g., VM must be running) or when a restart is preferred over other operations.

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