workflow_batch

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

No annotations exist, so the description must disclose behaviors. It explains the two-step dry-run/confirmation mechanism but does not mention potential destructive impacts, permissions needed, or error handling for the batch operations.

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 concise and well-structured: a one-sentence purpose, a bullet list of operations, and two sentences on usage. Every sentence adds value with no redundancy.

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 the complexity (5 parameters, nested objects, no output schema), the description is fairly complete but lacks details on return values (e.g., success counts, errors) and whether updates are synchronous or require confirmation.

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 coverage is 100% with descriptions. The description adds value by explaining each operation's purpose and the dry_run/confirmation workflow, providing more context than the schema alone.

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 clearly states the tool applies batch operations to pattern instances in Workflow Engine v2, listing specific operations like apply_fixes, skip_instances, flag_for_review, and group_by_type. This distinguishes it clearly from sibling tools like workflow_cancel or workflow_start.

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 provides good usage context: mentions pattern-based workflows, recommends dry_run=true for preview, and explains confirmation_token for execution. However, it doesn't explicitly state when not to use this tool or mention alternatives for single-instance operations.

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