stop_vm

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

No annotations provided; description mentions hard-stop but lacks disclosure of data loss risk, auth needs, or side effects beyond returning a task UPID.

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?

Single sentence is concise and front-loaded, but could be slightly expanded for completeness without adding bulk.

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 only 2 required parameters and a straightforward action, the description covers the core purpose but lacks parameter descriptions and usage context to be fully complete.

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%, and the description adds no information about the parameters (node, vmid), leaving the agent without meaning beyond the schema titles.

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 the action (hard-stop, immediate power off) and resource (QEMU VM), differentiating from sibling tools like shutdown_vm that perform graceful shutdown.

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 implies immediate power off but does not explicitly state when to use versus alternatives like shutdown_vm or reboot_vm, leaving the agent without clear when-to-use guidance.

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