vm_stop

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

Despite no annotations, description fully discloses behavioral traits: clean shutdown depends on guest tools, force is hard power-off, captures prior power state, refuses self VM, and dry_run behavior with IP hint. No contradictions.

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?

Description is detailed but well-structured with paragraphs and bullet-style args. Front-loaded with purpose and important notes. Could be slightly tighter but earns its length.

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?

Covers purpose, parameters, behavioral notes, edge cases (self VM, dry_run), and distinguishes from siblings. No output schema, so return values not explained, but otherwise complete for a stop action.

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 0%, but description explains each parameter: vm_id as UUID, force as hard power-off, dry_run as preview, target as XO target. Adds significant meaning beyond schema.

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?

Clearly states it stops a VM with clean shutdown or force, and identifies inverse as vm_start. Differentiates from siblings like vm_reboot and vm_migrate.

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?

Provides guidelines on when to use clean vs force, notes requirement of guest tools for clean shutdown, and warns against stopping self VM or using dry_run with self guard. Could be more explicit about alternatives.

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