Create Groups Migrations

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Start Data Migration.' This implies a mutating, possibly long-running operation, but it does not disclose side effects, permissions, whether existing data is affected, or whether the migration is asynchronous. The lack of any behavioral detail beyond 'start' is a significant gap for an import/migration tool.

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 short and front-loaded, but this is under-specification rather than effective conciseness. For a tool with four parameters and multiple migration source types, a three-word description is not appropriately sized. Every word is information-poor, and the description fails to earn its place as a useful guide.

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 migration tool is complex: it accepts a binary archive, supports ten different migration_type values, and has an optional tag behavior. The description provides none of the needed context, leaving the agent without enough information to select parameters or understand consequences. Even though an output schema exists, the lack of behavioral and operational context makes this definition completely inadequate.

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 by explaining the parameters, but it does not. The schema itself lists migration_type, archive, accept-language, and add_migration_tag, yet the description gives no indication of what the archive should contain, how migration_type choices map to behavior, or what add_migration_tag does. The agent has no textual help beyond raw parameter names and enum values.

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 'Start Data Migration' identifies a verb and a resource, which is more than a pure tautology. However, it is vague: it does not state that this starts a migration into a group, nor does it explain what kind of data migration is involved. Since there are no migration-related siblings, differentiation is not the issue, but the scope of the operation remains unclear.

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 about when to use this tool, what prerequisites exist, or what preparation is needed before calling it. The description merely says to start a migration, leaving the agent to infer context from the schema. There are no alternative sibling migration tools to contrast against, but even basic usage conditions are absent.

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