ai_migrate

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention whether migrations are destructive (e.g., overwriting existing data), whether they require permissions, whether they are synchronous or asynchronous, or what side effects may occur. 'Unified' implies a single tool for many behaviors but obscures what each type actually does.

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 only one short phrase, so it is concise. However, it is under-specified: 'Unified AI-powered migration operations' is more of a vague label than a proper behavioral description. There is minimal content to structure, and what exists is generic.

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?

This is a complex, multi-purpose tool with 7 parameters, nested objects, 4 enum types, and no output schema. The description does not explain return values, behavior differences across types, idempotency, or failure modes. For a tool this broad, one phrase is grossly insufficient.

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 description coverage is 100%, so every parameter already has basic descriptions (type, source, target, filters, options, instruction, transformation). The description adds nothing beyond the schema. However, the schema itself provides meaningful parameter descriptions with conditional guidance (instruction required for data, transformation for other types), so the baseline of 3 is appropriate.

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 says 'Unified AI-powered migration operations' which indicates a migration verb plus a resource family, but 'unified' suggests it conflates multiple distinct operations (data, workflows, templates, quality_rules) into one tool. It lacks specificity about what migrating means for each type and does not distinguish from the many sibling management tools (manage_quality_rules, manage_workflows, manage_templates) that overlap in domain.

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 vs the many sibling management tools or auto_detect_workflow. The description provides no excluded alternatives or specific triggers. The type enum hints at usage domains, but the description itself gives no usage context whatsoever.

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