Reset VM

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

Annotations already declare destructiveHint=true, confirming the destructive nature. The description adds value by distinguishing 'soft' (graceful) and 'hard' (forced) modes and noting returns a confirmation message. However, it does not explicitly warn about potential data loss on hard reset or mention handling of encrypted VMs (vm_password). With annotations covering the safety profile, this is adequate but not rich.

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 concise and well-structured: purpose, args, returns. No filler words. It is front-loaded with the main action. However, it is incomplete (missing vm_password), which slightly detracts from the efficiency of the structure, earning a 4 instead of 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 destructive tool with no output schema, the description should explain more context: prerequisites, risks, and all inputs. It does explain return values and mode differences but omits the password parameter and provides no guidance on when to use this tool versus siblings. The missing usage guidance and parameter make it incomplete for a moderately complex operational task.

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%, so baseline is 3. However, the description lists only vmx_path and mode, omitting vm_password entirely. This is misleading because it suggests only two parameters exist, especially since encrypted VMs may require the password. It adds a bit of semantic detail for mode (soft/hard) but fails to acknowledge the third parameter, which is a significant gap.

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 'Reset (reboot) a VMware Fusion virtual machine' with a specific verb and resource. It distinguishes itself from sibling tools like fusion_start_vm, fusion_stop_vm, and fusion_suspend_vm by the reset action. The scope is unambiguous.

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?

There is no guidance on when to use reset versus stop/start/suspend or other alternatives. No prerequisites are mentioned (e.g., the VM must be running or Fusion must be open). The description focuses on mechanics but not on decision-making, leaving the agent without clear usage criteria.

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