migration_executeBatch

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

Discloses async nature, auto-chunking behavior, return values (batch IDs), and dryRun effects. However, with no annotations provided, it omits critical safety context: whether execution is destructive (modifies process instances), permission requirements, or partial failure handling.

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?

Four efficient sentences front-loaded with core action. Each sentence adds distinct value: execution model, chunking behavior, return values, and dryRun capability. No redundancy or filler.

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 immediate operation details well despite absent annotations/output schema, but misses workflow context (relationship to plan generation and status monitoring tools) and lacks destructive operation warnings expected for complex migration tasks.

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?

Zero parameters in schema triggers baseline 4 per rubric. Description references dryRun mode and instance lists without mapping them to specific inputs, but this doesn't degrade below baseline given the empty schema constraint.

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?

Clear specific verb (Execute), resource (migration plan), and execution mode (asynchronously). Distinguishes from sibling migration_generatePlan (planning) and migration_validatePlan (validation) by focusing on actual execution.

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 through dryRun mode (validation vs execution) and auto-chunking (for large instance lists), but lacks explicit workflow guidance—doesn't mention prerequisites like migration_generatePlan or status checking via migration_awaitBatch.

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