migration_suspendBatch

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

Discloses return format ('per-batch success or error') which compensates partially for missing output schema. However, lacks operational details crucial for a mutation: whether suspension is immediate/async, effect on running jobs, or reversibility (despite no annotations to carry this burden).

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 sentences with zero waste: first defines action/target, second specifies return value. Appropriately sized for the complexity.

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?

Adequate for basic tool selection but incomplete for a mutation operation: no annotations, no output schema, and missing behavioral context like state transitions or side effects. 'Returns... error' covers minimum return value disclosure.

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?

0 parameters present, triggering baseline score 4 per rubric. Description mentions 'by ID' implying identification mechanism, though schema is empty—this adds context but doesn't fully resolve the parameter documentation gap.

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?

Specific verb ('Suspend') + resource ('migration batches') + scope ('by ID'). Clearly distinguishes from siblings like migration_resumeBatch, migration_deleteBatch, and migration_executeBatch through distinct action semantics.

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 explicit guidance on when to suspend vs. delete, prerequisites (e.g., batch must be active), or relationship to migration_resumeBatch. 'By ID' implies need for IDs but doesn't clarify if migration_listBatches should be called first.

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