reset_vm

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

No annotations are provided, so the description carries the full burden. It states 'hard reset' implying a destructive action, but does not disclose side effects (e.g., potential data loss), required permissions, or state changes to the VM. For a destructive tool, more transparency is needed.

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 extremely concise with two short sentences and an argument list. It front-loads the main purpose and avoids fluff, making it easy for an agent to parse 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?

Given the complexity of a reset operation (destructive, state-changing) and the lack of annotations, the description is incomplete. It does not explain return values (though an output schema exists), prerequisites, or behavior under failure conditions. A more complete description would include warnings or success/failure indicators.

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 adds minimal meaning over the schema by stating that 'node' is the node name and 'vmid' is the VM ID. Since schema description coverage is 0%, this provides basic clarification, but does not offer examples, constraints, or format details beyond what is obvious from 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 tool performs a hard reset of a VM, using a familiar analogy ('like pressing the reset button'). It distinguishes from sibling tools like reboot_vm, shutdown_vm, and stop_vm by specifying the action as a hard reset, which implies a forceful restart without graceful shutdown.

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 provides a simile (like pressing the reset button) that hints at when to use it (forceful reset), but lacks explicit guidance on when vs not to use it, or how it compares to reboot_vm or shutdown_vm. No exclusions or prerequisites are mentioned.

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