reset_vm

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

The annotation destructiveHint: false suggests the tool is not destructive, but the description adds only 'immediate', implying a forceful reset that may cause data loss if the VM is running. This is a potential inconsistency, but the description does not elaborate on consequences. With annotations present, the description adds minimal behavioral context beyond the schema.

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, concise sentence that immediately states the purpose. Every word is meaningful and front-loaded.

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 potential impact (forceful VM reset), the description lacks important context such as effect on running processes, data integrity, or prerequisites. With no output schema, the description should compensate, but it does not.

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 has 100% coverage with descriptions for node and vmid. The description adds no additional parameter information, so the baseline score of 3 is appropriate.

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 'Reset a VM (immediate)' clearly states the action and resource, and the parenthetical '(immediate)' hints at a forceful restart, distinguishing it from siblings like reboot_vm or shutdown_vm. However, it could be more explicit about the behavior.

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 provided on when to use reset_vm versus alternatives (e.g., reboot_vm, shutdown_vm). The description lacks context for appropriate use or prerequisites.

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