github_migrations_start_for_authenticated_user

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

No annotations provided, so the description carries full responsibility. It only says 'Start a user migration' without disclosing whether the operation is asynchronous, what side effects occur, or what authentication is needed. This is insufficient for safe 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 concise (four words), but it sacrifices completeness for brevity. Every sentence should earn its place; here, the single sentence is too vague to be fully valuable.

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 complex domain (migrations) and lack of an output schema, the description fails to explain what a user migration is, how to specify it via the body parameter, or what the tool returns. The minimal description leaves the agent underinformed.

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 has 100% description coverage for the 'body' parameter, but the tool description adds no extra meaning—it doesn't specify required fields or expected structure. With baseline 3 due to coverage, the lack of additional context reduces the score.

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 ('start') and resource ('user migration'), and distinguishes it from sibling tools like 'github_migrations_start_for_org' which targets org migrations. However, it does not explain what a user migration entails.

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 on when to use this tool versus alternatives like listing migrations or canceling imports. There is no mention of prerequisites or context for invoking this tool.

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