esxi_power_off

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

With no annotations, the description carries the full burden. It discloses a key behavior: 'Tries graceful shutdown first, falls back to force.' Yet it does not mention potential data loss, permission requirements, or reversibility, leaving significant risk information unstated.

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, well-structured sentence that front-loads the purpose and includes the key behavioral nuance. Every word earns its place with 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?

For a straightforward VM power-off operation, the description covers the essential behavior and all required parameters are defined in the schema. It omits details like potential data loss or return format, but these are not critical for this simple tool. The lack of output schema is acceptable given the simplicity.

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 100%, so baseline is 3. The tool description adds meaning to the 'force' parameter by explaining it is the fallback behavior, which is not present in the schema's description. This extra context justifies a 4.

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 states 'Power off a VM on ESXi' with a specific verb and resource, and adds the graceful-then-force behavior. This clearly distinguishes it from sibling tools like esxi_power_on, esxi_restart_vm, and esxi_suspend_vm.

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 description clearly implies when to use this tool (to power off a VM) and distinguishes it from suspend/restart/power-on by naming the action. However, it does not explicitly state when NOT to use it or name alternatives, so it falls short of a 5.

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