Reset VM

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

Annotations already indicate destructive behavior (destructiveHint=true), but the description adds no additional context about what is destroyed (e.g., unsaved VM state). No contradiction, but no added value.

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 brief (one sentence), but it sacrifices informativeness for brevity. Important details about modes and behavior are omitted.

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 presence of a destructiveHint and a parameter with an enum, the description is highly incomplete. It fails to explain what reset does, how it differs from other VM tools, and what the mode parameter controls.

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 50% (only vmxPath has a description). The tool description does not explain the 'mode' parameter or its enum values (soft vs hard), missing an opportunity to clarify behavior.

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 VMware VM' clearly states the verb and resource, distinguishing it from sibling tools like start, stop, pause. However, it lacks detail on what reset entails (e.g., power cycle, state loss).

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 reset versus alternatives like stop/start or pause. The description does not mention context or prerequisites for using this tool.

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