esxi_restart_vm

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

With no annotations, the description must carry behavioral transparency. It only states 'Restart a VM' but does not disclose that restart is a mutating operation causing downtime, that graceful=false performs a hard reset, or any other side effects. The description provides minimal insight beyond the tool name.

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 a single, concise sentence that front-loads the action and target. Every word is necessary, with no redundant content or excessive length.

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 simplicity of the operation and full schema coverage, the description is somewhat adequate, but it does not mention the expected return value or whether the call is synchronous. Since there is no output schema, the description should provide more context about post-restart behavior or response format, leaving moderate gaps.

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 input schema covers all three parameters (vm_id, graceful, device_id) with descriptions, achieving 100% schema description coverage. The description itself adds no parameter context, but the schema already handles semantics, so baseline 3 is appropriate.

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 uses a specific verb 'Restart' with the resource 'VM on ESXi', clearly identifying the tool's action. It distinguishes it from sibling tools like esxi_power_on, esxi_power_off, and esxi_suspend_vm, which have different verbs.

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?

No guidance is provided on when to use restart versus other power actions (power on/off/suspend), or when to set graceful to true/false. The description offers no context or exclusions for choosing this tool over alternatives.

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