pdm_pve_lxc_remote_migrate

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is a mutation, default is dry-run (PLAN), confirm=True submits and returns a PDM task reference, and delete=True is irreversible. It also notes that pve_task_status cannot poll the returned UPID, so pdm_tasks_list must be used.

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 and well-structured: first sentence states the purpose, then sibling differentiation, then required inputs, then optional behaviors, then task tracking. Every sentence earns its place with no redundancy.

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?

The description is complete for the tool's complexity. It covers the main action, required parameters, default behavior, destructive option, and post-submission tracking. With an output schema present, the return value is already defined.

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 coverage is 100%, so baseline is 3. The description adds value by explaining mapping syntax (e.g., 'vmbr0:vmbr0'), clarifying delete=True as irreversible, and explaining dry-run vs confirm behavior. This goes beyond the schema descriptions.

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 it migrates a container to a different PDM-registered remote (datacenter-to-datacenter). It distinguishes from siblings by specifying alternatives for VMs and same-cluster moves, making the tool's purpose unambiguous.

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 explicitly says when to use this tool vs alternatives: 'For a VM use pdm_pve_qemu_remote_migrate; for a same-cluster move use pdm_pve_lxc_migrate.' It also mentions required parameters (target_bridge, target_storage) and default behavior (dry-run).

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