github_migrations_update_import

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

With no annotations, the description must disclose behavioral traits, but it only implies a mutation ('update') without clarifying side effects, idempotency, exact changes made, or required permissions. The agent lacks critical safety information.

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 only three words, which is inadequate. This is not conciseness but underspecification; it lacks any structure or informative content, failing to justify its existence.

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?

For a mutation tool with no annotations and no output schema, the description should provide substantial context about the update operation, but it provides none. The agent cannot determine what the tool does, how to use it correctly, or what the outcome will be.

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 description adds no meaning beyond the schema field names. The 'body' parameter is described as 'Request body (JSON object)', but the description fails to explain what properties the body should contain, leaving a significant gap for a tool that likely requires specific fields to update an import.

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 'Update an import' is vague and essentially restates the tool name. It does not specify what kind of import or what aspects can be updated, failing to differentiate from sibling tools like github_migrations_cancel_import or github_migrations_get_import_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?

No guidance is provided on when to use this tool vs alternatives. There is no mention of prerequisites, context, or scenarios where updating an import is appropriate, leaving the agent without decision support.

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