Stop VM (force)

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

The description discloses the action (immediate power off) but does not mention potential data loss or consequences beyond what is obvious. Annotations have destructiveHint=false, which aligns with the tool not destroying the VM, but the description could warn about unsaved data.

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 sentence with no wasted words, front-loading the essential information about the tool's action.

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?

The description covers the core action but lacks warnings about non-reversibility or data loss, and does not mention return values. Given the tool's simplicity and lack of output schema, it is minimally adequate.

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 0% and the description adds no information about parameters node or vmid, leaving the agent to infer from naming alone.

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 it's a hard stop (immediate power off) equivalent to pulling the plug, distinguishing it from graceful shutdown options like shutdown_vm. The verb and resource are specific.

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 implies usage for emergency or unresponsive cases via 'equivalent to pulling the plug', but does not explicitly state when to use versus alternatives like shutdown_vm or provide exclusions.

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