template_vm

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

No annotations are provided, so the description bears the full burden of disclosing behavioral traits. It only states the conversion action without explaining side effects (e.g., irreversibility, whether the VM becomes non-bootable, or if concurrent operations are blocked). This lacks critical context for a mutation 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?

The description is a single, tightly written sentence that directly conveys the core purpose with no wasted words. It is perfectly sized for the tool's simplicity.

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 that this is a mutation tool with no annotations, no output schema, and zero parameter descriptions, the one-line description is inadequate. It omits prerequisites, side effects, and any detail about the expected outcome beyond the conversion itself.

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 0%, and the tool description does not explain the meaning or format of `node` and `vmid`. The agent must infer their roles from context, which is insufficient for a low-coverage 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 a specific verb 'convert' and identifies the resource as 'QEMU virtual machine' with a clear outcome ('reusable template'). This distinguishes it from sibling tools like create_vm, clone_vm, and template_container.

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 purpose implies usage (to create a template from a VM), but there is no explicit guidance on when to prefer this over alternatives such as clone_vm or template_container, nor any mention of prerequisites or conditions like the VM needing to be stopped.

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