Migrate all VMs/CTs off node

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

The description adds only 'live' migration, which is minimal behavioral context. It does not address what happens if some migrations fail, whether migration is sequential or parallel, or any requirements like target node availability. Given no annotations cover these details, the description is insufficient.

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 a single sentence that starts with the verb 'Bulk-migrate'. However, it sacrifices necessary detail for brevity, making it less helpful than it could be.

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?

For a complex bulk migration tool with 4 parameters and no output schema, the description is inadequate. It does not cover behavior, parameter meanings, error conditions, or required preconditions, leaving the agent with insufficient information to use the tool correctly.

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?

With only 25% schema coverage, the description should compensate by explaining parameters, but it does not mention any parameters. It vaguely implies the node parameter as source and 'to others' hints at distribution but fails to detail target, max_workers, or with_local_disks.

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 (bulk-migrate), resource (all VMs/containers off this node), and method (live). It effectively distinguishes from sibling tools like migrate_vm or migrate_container which handle single migrations.

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 provides no guidance on when to use this tool versus alternatives like migrate_vm or migrate_container. It does not mention prerequisites, potential risks, or scenarios where this tool should be avoided.

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