vm_start

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

The description labels the operation as a write, indicates the return value, and explains the optional node parameter with auto-location behavior. However, it does not discuss permissions, side effects, or behavior when the VM is already started.

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 concise and well-structured, with a header line and an Args section that lists parameters and their meanings. Every sentence contributes useful information without 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?

Given no annotations or output schema, the description provides a good overview. It could mention that the VM should be in a stopped state to start and explain the UPID return format, but it is sufficiently complete for a simple operation.

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?

With 0% schema description coverage, the description adds essential semantics: vmid is numeric, target comes from config, node is optional with auto-location. This compensates well for the empty schema descriptions.

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 'Start a VM' with '[WRITE]' and specifies the return type 'Proxmox task UPID'. It distinguishes the tool from its siblings by naming the inverse 'vm_stop'.

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 mentions only the inverse tool vm_stop, but does not provide guidance on when to use this tool over other related sibling tools like vm_reboot or vm_shutdown. No prerequisites or context for use are given.

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