proxmox_create_vm

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

With no annotations, the description carries full burden. It only states it creates a VM and needs elevated permissions, but lacks details on success response, error states, concurrency, or whether operation is idempotent. Minimal disclosure for a creation tool.

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, front-loaded with the core action. No unnecessary words or repetition. Efficient and to the point.

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?

No output schema and no description of return value (likely VM ID). For a creation tool, the agent would need to know what is returned. Also lacks details on required permissions or prerequisites. Incomplete given the tool's complexity.

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 coverage is 100%, so baseline is 3. The description does not add any parameter meaning beyond what the schema already provides. No extra context for how parameters like 'iso' or 'net0' interact.

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?

Description clearly states 'Create a new QEMU virtual machine', specifying the verb 'Create' and the resource 'QEMU virtual machine'. This distinguishes it from sibling tools like proxmox_create_lxc (container) or proxmox_guest_clone (clone existing 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?

Mentions 'requires elevated permissions' but does not explicitly guide when to use this tool vs alternatives like proxmox_guest_clone or proxmox_get_next_vmid (referenced in schema but not in description). No when-not-to-use or comparison with siblings.

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