proxmox_guest_template

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

With no annotations, the description must convey behavioral traits. It fails to disclose that converting a VM to a template modifies the original VM in-place (destructive) or that the VM must be stopped. The agent may incorrectly assume a copy is created.

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, efficient sentence that is front-loaded. However, it could afford to include additional critical details (like requiring the VM to be stopped) without becoming overly long.

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 the lack of annotations and output schema, the description is insufficient. It omits prerequisites (e.g., VM must be stopped), behavior (in-place conversion), and success/failure indicators, leaving key gaps for the agent.

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 67%: node and vmid have descriptions, type does not. The description adds value by clarifying the type parameter ('type=vm|lxc'), but does not enhance understanding of node or vmid beyond 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 clearly states the action ('Convert') and the specific resource ('VM or LXC container to a template'), including the type parameter hint. It distinguishes this tool from siblings like proxmox_guest_clone, which is for cloning, not converting to template.

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 a prerequisite ('requires elevated permissions') but does not provide explicit guidance on when to use this tool versus alternatives like proxmox_create_vm or proxmox_guest_clone. Usage context is implied but not explicitly stated.

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