migrate_twb_guided

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

The description discloses a key behavioral trait: it pauses for warning confirmation. This is beyond what annotations provide (none). However, it does not mention side effects, required permissions, or what happens after confirmation. The output schema is present but not referenced.

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 very short (one sentence, 13 words) and front-loaded with the primary action. It is concise, though it could benefit from a bit more detail without becoming verbose.

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 has 6 parameters (2 required) and an output schema, the description lacks necessary context for an agent to use it correctly. It does not explain the migration workflow, what warnings trigger pauses, or how to handle confirmation. Sibling tools like 'apply_twb_migration' and 'preview_twb_migration' suggest alternatives, but no comparison is made.

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%, and the description provides no additional meaning for any of the 6 parameters. The description does not explain 'mapping_overrides', 'scope', 'apply_if_no_blockers', or 'output_path'. The schema alone is insufficient.

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 tool runs a built-in migration workflow and pauses for warning confirmation. It uses specific verbs ('Run', 'pause') and identifies the resource ('migration workflow'). However, it does not differentiate from siblings like 'apply_twb_migration' or 'preview_twb_migration', which may overlap.

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'. There is no mention of prerequisites or when not to use it. The description implies usage for guided migration, but lacks explicit context.

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