pdm_pve_lxc_remote_migrate

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

No annotations provided, so the description carries full burden. It labels the tool as MUTATION, notes destructive behavior with delete=True, and explains dry-run vs submit. Could mention synchronicity or error states.

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?

Very concise, front-loaded with 'MUTATION', and efficiently conveys key information in three sentences.

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?

Core behavior is covered, and output schema exists. However, prerequisites like requiring both remotes to be registered or network connectivity are not mentioned. With 10 parameters, more context on other params would improve completeness.

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?

Only 10% of parameters have schema descriptions. The description covers target_bridge, target_storage, delete, and confirm with examples and effects, but leaves vmid, remote, target_remote, online, target_vmid, and proximo_target unexplained.

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?

Clearly states it migrates a container to a DIFFERENT PDM-registered remote, distinguishing it from local migration tools like pdm_pve_lxc_migrate and from VM migrations like pdm_pve_qemu_remote_migrate.

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?

Describes when to use: for container migration across datacenters. Mentions dry-run by default and confirm=True to submit. Could be more explicit about not using for local migrations or for VMs.

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