github_migrations_start_import

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

No annotations are provided, and the description fails to disclose any behavioral traits such as whether the operation is asynchronous, what permissions are required, or if it has side effects (e.g., creating background jobs). The description 'Start an import' is too vague for safe agent invocation.

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 (4 words), which is concise but at the expense of completeness. It is front-loaded but lacks necessary details to be useful.

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 complexity of the tool (starting a migration import) and the presence of many sibling tools, the description is severely incomplete. It does not explain what a 'migration import' entails, what parameters are required in the body, or what the return value indicates. The lack of an output schema further reduces completeness.

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?

Although schema coverage is 100%, the parameter descriptions are minimal ('owner', 'repo', 'Request body (JSON object)'). The description adds no extra meaning beyond the schema, and the 'body' parameter lacks details on its expected structure (e.g., required fields like vcs_url).

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 tool name 'github_migrations_start_import' clearly indicates it starts a migration import, and the description 'Start an import' aligns with that. However, the description could be more specific (e.g., 'Starts a source import using the GitHub Migration API') to differentiate from other import types like repository imports.

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 like 'github_migrations_cancel_import' or 'github_migrations_get_import_status'. It does not mention prerequisites or context for starting an import.

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