convert_container_to_template

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

With no annotations, the description must disclose behavior. It mentions 'irreversible', which is critical, but omits other important traits like required permissions, whether the container must be stopped, or what happens to the container post-conversion.

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?

Extremely concise: one sentence for the action plus two lines for parameters. Front-loaded with the main purpose, no redundant words.

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 2-parameter tool with an output schema, the description is adequate but lacks prerequisites and constraints (e.g., container existence, state requirements). It does not mention return values, but the output schema may cover that.

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?

Since schema coverage is 0%, the description adds meaning by naming parameters ('node', 'vmid') and providing brief descriptions. However, 'node: The node name' could be more precise (e.g., Proxmox cluster node).

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'), the resource ('container'), and the outcome ('template'), differentiating it from the sibling 'convert_vm_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?

No guidance on when to use this tool versus alternatives like 'convert_vm_to_template' or prerequisites (e.g., container must be stopped). The only usage hint is 'irreversible', which is a warning, not a guideline.

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