suspend_vm

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It confirms a mutation operation ('Suspend'), but says nothing about VM state persistence, handling of running processes, permission requirements, or reversibility via resume_vm; for a power-state mutation this leaves important behavioral traits undocumented.

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 four-word sentence with no filler, and the core action is front-loaded. For a simple one-parameter tool, this is appropriately sized and immediately readable.

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 no annotations, no output schema, and several closely related sibling tools, the description is too sparse to fully guide selection or invocation. At minimum it should distinguish suspend from stop_vm and resume_vm and indicate what suspend does to the VM's state, which it does not do.

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 100%, with the single 'vm' parameter fully documented as 'VM name or UUID.' The description adds no extra syntax, format, or constraint information beyond the schema, so the baseline score of 3 applies when the schema does the heavy lifting.

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 a specific verb and resource: 'Suspend a virtual machine.' It is clearly distinct from read-only siblings like list_vms and get_vm_info, but it does not differentiate itself from closely related power-state siblings such as stop_vm and resume_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?

No usage guidance is provided: there is no statement of when to use this tool versus stop_vm, resume_vm, or reset_vm, nor any prerequisites or exclusions. The verb itself implies a power-state action, but the agent receives no explicit routing help among the many VM control siblings.

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