Convert container to template

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

Discloses high risk and the side effect that the original becomes read-only, going beyond the annotations which only mark it as destructive. It also instructs on user confirmation, adding behavioral context.

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 two sentences with no wasted words. It front-loads the purpose and immediately adds risk and user instruction. Every sentence contributes value.

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 tool's destructive nature and lack of output schema, the description provides enough context for safe invocation: it explains the action, risk, and need for confirmation. It could mention what happens to the container after conversion, but the core context is there.

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 description does not explain any of the three parameters (node, vmid, confirm). With schema description coverage at only 33%, the description should compensate but fails to do so, leaving the agent to infer from parameter names alone.

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: converting an LXC container to a template, and it distinguishes from the sibling 'convert_vm_to_template' by specifying 'LXC container'. The verb 'Convert' and resource 'container' are specific.

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?

Explicitly instructs to ask user for confirmation before invoking, providing clear context for when it's appropriate. However, it does not explicitly compare with alternatives like 'convert_vm_to_template' or mention when not to use this tool.

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