migration_resumeBatch

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

Provides some behavioral context by stating it 'Returns per-batch success or error,' but missing critical details for a batch mutation tool: whether operation is synchronous/async, side effects, what happens if batch isn't suspended, or permission requirements. No annotations provided to cover these gaps.

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?

Extremely efficient: two sentences with zero waste. First sentence covers purpose and target, second covers return value. Every word earns its place.

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?

Covers basic operation and return value (compensating for missing output schema), but lacks operational details expected for a batch mutation tool: error conditions, batch size limits, state transition prerequisites, or concurrency behavior.

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 has 0 parameters (baseline 4), but description states 'by ID' implying input parameters that aren't reflected in the empty schema, creating ambiguity about how IDs are passed (path vs body). Description compensates slightly by indicating the 'one or more' cardinality.

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?

Description clearly states the specific action (Resume), target resource (migration batches), and prerequisite state (suspended), distinguishing it from siblings like migration_suspendBatch or migration_deleteBatch.

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?

Implies usage context by specifying 'suspended' batches and IDs, but lacks explicit guidance on when to choose this over alternatives like migration_executeBatch or migration_awaitBatch, and doesn't mention where to obtain batch IDs.

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