Stop VM

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

The destructiveHint annotation is true, aligning with 'stop'. However, the description adds no behavioral context beyond the annotation, such as the difference between soft and hard stop, potential data loss, or required permissions. Minimal 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 a single short sentence, which is concise but at the expense of required detail. It lacks structure and does not earn its place by providing essential guidance for agent invocation.

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 destructive nature, two parameters (one with enum), and 13 sibling tools, the description is severely incomplete. It fails to explain return values, parameter semantics, or use cases, leaving the agent with insufficient information to use the tool correctly.

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 description coverage is 50% (only vmxPath is described). The description mentions no parameters at all, failing to explain the 'mode' enum or how to use the parameters. With low coverage, the description should compensate but does not.

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 'Stop a VMware VM' is clear about the verb (stop) and resource (VMware VM), but it does not differentiate from sibling tools like pause_vm, suspend_vm, or reset_vm. The name alone conveys similar information, making the description somewhat redundant.

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 stop_vm versus alternatives. The description lacks any context about prerequisites, scenarios, or exclusions, leaving the agent without decision-making support.

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