Start Guest

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

Annotations already cover mutation (readOnly=false), non-destructiveness, and idempotency. The description adds a useful behavioral requirement: elevated permissions are needed. It does not describe async behavior or failure modes, but the extra permission context is meaningful beyond the annotations.

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?

A single sentence with no filler; the action and target resource are front-loaded, and the elevated-permission note is compactly appended. Every word earns its place.

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 start operation with three required parameters, all parameters are semantically covered (node/vmid in schema, type in description) and annotations address idempotency and destructiveness. No further context is necessary to invoke the tool correctly.

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?

Node and vmid already have descriptions, while the type parameter lacks one; the description compensates by explicitly mapping type=vm to VM and type=lxc to LXC container. This fills the only semantic gap in the input schema.

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 the specific verb 'Start' with a clear resource ('a VM (type=vm) or LXC container (type=lxc)'), making the action and target unambiguous. This differentiates it from sibling lifecycle tools like proxmox_guest_stop, proxmox_guest_reboot, and proxmox_guest_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 only usage-related hint is 'requires elevated permissions', which is a precondition, not guidance on when to choose this tool over alternatives. None of the many sibling tools are mentioned and no when-to-use/when-not-to-use context is provided.

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