Move container disk

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

The description is minimal and does not disclose behavioral traits beyond the annotation hints. It does not mention that the source might be deleted (controlled by 'delete_source' parameter), potential side effects, or whether the operation is reversible. No contradiction with annotations.

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 very concise, but it lacks sufficient detail to be maximally helpful. It is front-loaded but too minimal for the complexity of the operation.

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 high parameter count (6), low schema coverage (17%), and no output schema, the description is incomplete. There is no information on return values, side effects, or prerequisites.

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 only 17%, and the description does not add any parameter semantics. It does not explain what 'node', 'vmid', 'storage', 'format', or 'delete_source' mean. The parameter 'disk' is partly described in the schema but not augmented.

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 ('Move') and the resource ('container volume') with a specific target ('different storage pool'). It distinguishes from siblings like 'migrate_container' (which moves to a different node) and 'move_vm_disk' (which is for VMs).

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 is provided on when to use this tool versus alternatives such as 'move_container_volume' or 'migrate_container'. There are no contextual hints about prerequisites or when not to use it.

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