vsphere_change_vm_power_state

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

The description adds transparency beyond the annotations by highlighting that power_off and reset can lose unwritten data, explaining the return behavior of guest actions, and stating the required permission mode. This aligns with destructiveHint=true and readOnlyHint=false without contradiction.

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 compact, well-organized, and front-loaded with the core purpose. Each sentence earns its place: a lead sentence, safety/usage guidance, a permission note, and a clear Args block. No redundant or irrelevant content.

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 complexity (multiple power actions, risk of data loss, various vm identifiers), the description fully covers usage scenarios, caveats, permissions, and parameter meanings. The presence of an output schema handles return values, so no additional output documentation is needed.

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?

The schema has no parameter descriptions (0% coverage), but the description's Args section provides detailed semantics for each parameter, including accepted vm formats (name, managed object id, UUID, inventory path), the full action enum, and the purpose of wait and timeout_seconds.

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 changes the power state of a virtual machine with a specific verb and resource. It lists the exact actions (power_on, power_off, suspend, reset, shutdown_guest, reboot_guest, standby_guest), which distinguishes it from sibling tools that handle listing, snapshots, or deletion.

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?

Explicit guidance is provided on when to use guest actions vs hard power operations, with a clear recommendation to prefer shutdown_guest/reboot_guest when VMware Tools is running. It also explains that wait does not apply to guest actions, giving actionable usage context.

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