migration_deleteBatch

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It identifies the destructive nature ('delete') and response format, but omits critical safety details for a deletion operation: whether cancellation is irreversible, effects on in-progress migrations, or required permissions.

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?

Two efficiently structured sentences with zero waste. The first sentence front-loads the action and scope, while the second addresses the return behavior. 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?

Given this is a destructive operation with no annotations, empty input schema, and no output schema, the description is minimally sufficient but lacks necessary safety warnings, side-effect documentation, or details on batch state requirements (e.g., can you delete running batches?).

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 0 parameters (baseline 4). The description adds the crucial semantic context that the operation targets specific resources 'by ID', which the empty schema does not convey. This is the only indication of how to specify which batches to delete.

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 uses specific verbs ('Cancel', 'delete') and identifies the resource ('migration batches') clearly. However, it does not distinguish this tool from siblings like 'migration_suspendBatch' or 'migration_resumeBatch', leaving ambiguity about when to choose destructive cancellation over suspension.

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 mentions the return value ('Returns per-batch success or error') but provides no guidance on when to use this tool versus alternatives like suspendBatch, nor does it mention prerequisites such as requiring batch IDs from migration_listBatches before invocation.

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