youfiliate_start_migration

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

Annotations already indicate destructiveness (destructiveHint: true). The description adds key details: the tool modifies YouTube descriptions, runs asynchronously, and requires explicit confirmation. It also mentions common errors. No contradictions.

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 and well-structured. It front-loads the core purpose, then provides critical usage notes, async behavior, prerequisites, and common errors in a scannable format. Every sentence adds value.

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?

The description covers the tool's purpose, key behavioral aspects, prerequisites, and common errors. It explains async tracking but does not explicitly state the return value (migration ID). Given that an output schema exists, this gap is minor.

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 input schema already describes all parameters in detail, including the critical 'confirm' field's purpose. The tool description reinforces these points and adds usage context but does not introduce new parameter semantics beyond what the schema specifies.

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's purpose: starting a migration to convert YouTube description links to smart links. It distinguishes from sibling tools like preview_migration and rollback_migration by noting that the migration runs asynchronously and requires confirmation.

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 clear usage guidelines: requires user confirmation after previewing scope, mentions tracking with get_migration_status, and lists common errors including prerequisites like YouTube connection. It strongly implies that preview_migration should be used first to determine scope.

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