esxi_power_vm

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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: shutdown is '优雅' (graceful) and both it and reboot_guest depend on VMware Tools, implicitly warning that they can fail or behave differently from the hard power_off/reset paths.

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?

A single, densely packed sentence that front-loads the resource and then the operation list with inline constraints. Nothing is wasted, though the parenthetical notation is terse enough to be slightly cryptic.

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?

An output schema exists so return values need not be described, and the graceful/hard distinction is a useful addition for a destructive tool. Still missing: what expected_name guards against (apparently a safety confirmation), what dry_run=true actually does, and which operations are irreversible.

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%, so the description must carry the load. It partially does by supplying the valid values for 'operation' (power_on / shutdown / power_off / reboot_guest / reset), which the schema lacks as an enum, but vm_id, expected_name, and especially dry_run (defaulting to true) are left completely unexplained.

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?

Names a specific verb+resource (power operations on an ESXi VM) and enumerates the five supported operations, which is the key discriminator versus siblings like esxi_configure_vm or esxi_delete_vm. It does not, however, explicitly contrast itself with any sibling tool.

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 parenthetical '需Tools' (requires VMware Tools) on shutdown and reboot_guest is a real prerequisite hint that tells the agent those two paths need guest tooling, unlike power_off/reset. But there is no guidance on when to prefer graceful shutdown over power_off, nor any exclusions or alternatives named.

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