vm_power_off

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

Annotations include destructiveHint:true and readOnlyHint:false. Description adds that default is graceful shutdown, force is hard power off, and target is optional. This provides behavioral context beyond annotations, though it lacks details on potential data loss or irreversible effects.

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 6 lines, well-structured with Args section. Every sentence provides essential information without redundancy or fluff. Front-loaded with purpose.

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 all input parameters and behavioral nuances (graceful vs force). Has output schema (not shown), which likely handles return values. Given context signals (3 params, 1 required), description is complete enough for selection and invocation.

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 has 0% description coverage. Description explains each parameter: vm_name is exact name, force boolean with default false meaning graceful, target optional for vCenter/ESXi. Adds meaning beyond schema structure.

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?

Description clearly states 'Power off a virtual machine' with specific verb and resource. Distinguishes from sibling 'vm_power_on' by explicitly naming power-off and detailing force vs graceful shutdown.

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 guidance on when to use force vs graceful shutdown. Does not explicitly mention when not to use this tool (e.g., for other operations like reboot), but context is clear. No alternative sibling directly mentioned, but the tool is self-contained.

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