github_migrations_start_for_org

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

No annotations exist, so the description must disclose behavioral traits. It only states 'Start an organization migration' without mentioning side effects, required permissions, or what the initiation entails. This is insufficient for an agent to understand the impact.

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, which is concise, but it lacks structure and important details. While there is no wasted text, it is too brief to be fully helpful.

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?

The tool has a nested body parameter and no output schema, yet the description provides no details on the body's structure or the migration process. It does not answer what happens after starting or how to monitor progress, leaving significant gaps.

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 100%, but the descriptions are minimal ('org' and 'Request body (JSON object)'). The tool description adds no additional meaning to the parameters, meeting the baseline of 3 as per schema coverage guidelines.

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 an organization migration' is clear about the action and resource, but it is too minimal and does not differentiate from sibling tools like github_migrations_start_for_authenticated_user or other migration operations. It lacks specificity on migration type or scope.

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 usage guidelines are provided. There is no information on when to use this tool versus alternatives such as github_migrations_start_for_authenticated_user or github_migrations_start_import, nor any prerequisites or context for its use.

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