initiate_cloud_migration

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states that the tool initiates a migration, but does not reveal whether the operation is synchronous or asynchronous, what permissions are needed, what happens to existing migrations, or what the response contains. The agent gains no insight into side effects or execution behavior.

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 sentence that is direct and to the point. It contains no extraneous words or information. For a simple tool with one parameter, this level of conciseness is appropriate and efficient.

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 lack of annotations, output schema, and any additional context, the description is far from complete. It does not explain what happens after initiation (e.g., returns a migration ID, starts an async process), what the expected outcomes are, or how to monitor progress. For a potentially impactful operation like a cloud migration, this is insufficient.

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 tool description does not add any parameter information beyond the schema. While the schema itself includes a description for store_api_key ('Metabase Store API key used to authenticate the migration'), the tool description ignores parameters entirely. For a tool with only one parameter, the description should at least reference the purpose of the API key or its role. The 0% schema description coverage further emphasizes the lack of parameter guidance in the description.

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 action ('Initiate') and the resource ('cloud migration to Metabase Cloud'). The verb and noun combination is specific, and the sibling names (cancel_cloud_migration, get_cloud_migration) make it distinct from related tools. However, it does not explicitly exclude other actions like checking status.

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 no guidance on when to use this tool versus alternatives (e.g., cancel_cloud_migration, get_cloud_migration). There is no mention of prerequisites, such as whether a migration must not already be in progress, or what conditions are required to initiate a migration. This leaves the agent without context for appropriate usage.

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