vm_power_off

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

Discloses graceful shutdown uses VMware Tools with 120s wait, that force risks filesystem damage, and that audit logging occurs. Adds significant context beyond destructiveHint annotation.

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?

Well-structured: [WRITE] tag, summary, detailed explanation, Args section, Returns. Every sentence adds value; no redundancy.

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?

Fully explains behavior, prerequisites, side effects, and return value. Differentiates well from 30+ sibling tools. No gaps given annotations and output schema hints.

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?

Covers all 3 parameters despite 0% schema coverage: vm_name is case-sensitive exact name, force defaults false with explanation, target from config.yaml with default. Provides complete semantics.

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?

Explicitly states 'Power off a VM' with two modes (graceful and hard). Distinguishes from siblings like vm_power_on and vm_delete by referencing them directly.

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 clear guidance on when to use graceful vs force, mentions retry with force if tools fail, and explains prerequisites (vm_delete requires VM off). Also advises use of vm_power_on for starting.

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