Migrate container between nodes

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

Annotations indicate the tool is not read-only and not destructive. The description adds that the container keeps running with online=true, which provides behavioral context. However, it does not disclose what happens to the source container after migration (e.g., deletion) or any permission requirements.

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 concise with two sentences that immediately state the core purpose. However, it could be better structured to include parameter guidance without becoming overly long.

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 has 7 parameters, no output schema, and moderate annotations, the description is incomplete. It does not clarify required parameters like target_node, nor does it explain return values or success criteria. The description needs to provide more context for complex migration operations.

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 7 parameters with only 29% description coverage. The description fails to explain key parameters like target_node, timeout, or with_local_disks. The only parameter mentioned is online, but without further detail. This leaves the agent without essential context for proper invocation.

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 ('Migrate an LXC container'), the resource ('container'), and distinguishes between online/offline modes. This differentiates it from siblings like migrate_vm (for VMs) and migrate_ha_resource.

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 implies usage for migrating containers but does not provide explicit guidance on when to use this tool versus alternatives like migrate_vm or migrate_ha_resource. No prerequisites or exclusions are mentioned.

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