migrate_twb_guided

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

No annotations are provided, so the description carries full burden. It mentions pausing for warnings, which hints at interactive behavior, but doesn't disclose critical traits like whether it's destructive, what permissions are needed, rate limits, or what happens during migration failures. For a migration tool with 6 parameters, this 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 a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for the tool's complexity, though it lacks detail.

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 6 parameters, 0% schema coverage, no annotations, and sibling tools with similar names, the description is incomplete. It doesn't explain the migration context, what 'TWB' refers to, or how outputs are handled (though an output schema exists). For a complex migration tool, this leaves significant gaps.

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 0%, so the description must compensate for all 6 parameters. It adds no meaning beyond the schema—doesn't explain what 'file_path', 'target_source', 'scope', or other parameters do, their formats, or relationships. This leaves parameters largely undocumented.

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 states the tool runs a migration workflow and pauses for warnings, which gives a general purpose. However, it's vague about what exactly is being migrated (TWB files? data sources?), doesn't specify the resource clearly, and doesn't distinguish from sibling tools like 'apply_twb_migration' or 'preview_twb_migration'.

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 is provided on when to use this tool versus alternatives like 'apply_twb_migration' or 'preview_twb_migration'. The description mentions pausing for warnings, which implies interactive use, but doesn't specify prerequisites, when-not scenarios, or explicit alternatives.

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