migrate_ha_resource

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

No annotations provided. The description does not disclose whether migration is synchronous, if it affects service availability, or any side effects. For a mutation tool, more behavioral context is needed.

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 extremely concise with no fluff. Every sentence serves a purpose, and the parameter list is structured clearly.

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's complexity (migration) and absence of annotations, the description is incomplete. It lacks information on return values, error states, or post-migration behavior, despite having an output schema.

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 description includes parameter explanations (sid: Resource ID, node: Target node) that add value beyond the schema's type and title. However, it does not specify formats or constraints, and schema coverage is 0%.

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 ('Request migration') and the resource ('HA resource' to a different node). It is specific and distinguishes from sibling tools like migrate_vm or migrate_container, though it does not differentiate from relocate_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?

No guidance on when to use this tool vs. alternatives like relocate_ha_resource. Missing prerequisites or conditions for migration (e.g., HA resource must be in a certain state, node availability).

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