pve_convert_container_to_template

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Convert container to template' implies a destructive/mutative operation that likely transforms a running container into a template, but the description doesn't specify whether this destroys the original container, requires the container to be stopped, has permission requirements, or what happens to container data. This is a significant gap for a mutation tool with zero annotation coverage.

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 extremely concise at just three words, which is appropriately sized for a simple operation. It's front-loaded with the core action. However, the extreme brevity borders on under-specification rather than optimal conciseness, as it omits important context that would help the agent.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain the conversion process, what a 'template' means in this context, whether the operation is reversible, what permissions are required, or what the result looks like. Given the complexity of converting a container to a template, the description should provide more contextual information.

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?

The input schema has 100% description coverage with clear parameter documentation ('node' and 'vmid'). The description adds no additional parameter information beyond what's already in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Convert container to template' clearly states the action (convert) and target (container to template), which is a specific verb+resource combination. However, it doesn't differentiate from its sibling 'pve_convert_vm_to_template' - both perform conversion operations on different resource types (container vs VM). The purpose is understandable but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, constraints, or comparison with related tools like 'pve_convert_vm_to_template' or 'pve_create_container_snapshot'. The agent must infer usage context from the tool name alone.

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