Create Content Migration

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

The description discloses asynchronous behavior: the tool returns immediately with a migration ID and a progress_url, and explicitly directs polling get_content_migration or progress_url for completion. The annotations include openWorldHint=true, meaning the operation may have side effects outside the system. The description notes the user can select content for selective import via get_migration_selective_data when selective_import is true, adding important behavioral context. However, it doesn't explicitly address that the operation is long-running or potentially destructive—although the destructiveHint=true annotation is consistent with a function that copies data into a course, so there's no contradiction.

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?

Three sentences, front-loaded with the main verb and resource. The first sentence lists specific migration types, the second explains asynchronous behavior, and the third tells the agent exactly what to do next—check get_content_migration or progress_url. No wasted words.

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?

For a tool with 5 parameters, no output schema, and no explicit output schema, the description explains the asynchronous return (migration ID and progress_url), tells how to track completion (poll get_content_migration or progress_url), and mentions the selective import flow (get_migration_selective_data). It also packages the key mental model of destination course_id. The description makes the tool fully usable without additional lookups.

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 coverage is 100%, so the baseline is 3. The description doesn't need to repeat parameter details. However, the description makes an important semantic clarification that the tool initiates a migration, frames the course_id as the destination course, and explicitly mentions 'poll get_content_migration or progress_url to track completion,' connecting the returned ID to the broader workflow. While the description doesn't add function-call details for each parameter, it clarifies the asynchronous workflow.

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 title and description clearly state the tool starts a content migration with a specific verb. The description says 'Start a content migration' and lists the migration types (course copy, Common Cartridge import, zip import, QTI conversion, or Moodle conversion), which uniquely identifies this tool even among migration-adjacent siblings like create_content_export and list_content_migrations. The phrase 'course copy' in the description maps to the sibling get_content_migration, providing clear differentiation.

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 indicates this is an asynchronous action ('Migrations are asynchronous — this tool returns immediately with a migration ID and progress_url'), which guides the agent on expected behavior. It also names the related tool get_content_migration for tracking completion. However, there is no explicit 'when not to use' guidance contrasting it with alternatives like create_content_export or upload_file, though the clear subject matter partially covers this.

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