qemu_vm_shutdown

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

Beyond the destructiveHint annotation, the description discloses the 40-second wait, the fallback force-stop behavior, and the fact that the VM remains locked by the session. This adds significant behavioral context not present in annotations. It does not contradict annotations and provides a clear operational sequence.

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?

Two sentences, front-loaded with the primary action, then the critical follow-up instruction. No wasted words; every phrase contributes to understanding the tool's behavior and workflow.

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 simple one-parameter tool, the description covers the complete workflow: graceful shutdown, timeout, fallback force-stop, scope (only this process), and required next step (vm_unlock). It is self-contained and sufficient for correct invocation despite the lack of an output schema.

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 0% description coverage for vm_id, and the description does not mention the parameter at all. While the parameter name is self-explanatory, the description fails to compensate for the lack of schema documentation, leaving the agent to infer that vm_id is the target VM identifier.

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 'shutdown' with a clear resource and detailed procedure: requests graceful guest shutdown, waits 40 seconds, then force-stops the QEMU process if needed. This clearly distinguishes it from sibling tools like qemu_vm_force_stop (which implies immediate termination) and qemu_vm_restart.

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 clear context on when to use: when a graceful shutdown with fallback is desired. It also explains the lock retention and instructs to call vm_unlock afterward, which is critical usage guidance. However, it does not explicitly name alternatives or state when not to use it (e.g., if immediate termination is needed), leaving some room for ambiguity.

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