Reset VM (hard)

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

The description reveals the tool performs a hard reset but omits behavioral details such as risk of data loss, non-graceful shutdown, or state dependencies. Annotations indicate it is not read-only and not idempotent, but the description adds no further context beyond a basic analogy.

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 that is highly concise. However, the extreme brevity sacrifices important details that would fit without becoming verbose, so it loses a point for under-specification.

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 the tool's simplicity (2 required params, no output schema) and the large set of sibling tools, the description is insufficient. It lacks context about VM lifecycle, when a hard reset is appropriate versus other actions, and potential consequences, leaving significant gaps for safe usage.

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 description does not mention the parameters (node, vmid) at all. With 0% schema description coverage, the agent receives no assistance in understanding what these parameters represent or how to set 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 'Hard reset — equivalent to pressing the reset button' clearly states the tool's purpose and the nature of the action. It distinguishes itself from sibling tools like reboot_vm (soft reboot) by specifying that it's a hard reset, providing immediate understanding of its function.

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 on when to use this tool versus alternatives such as reboot_vm or shutdown_vm. The description does not mention prerequisites, expected VM states, or warnings about data loss, leaving the agent to infer usage context without support.

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