bulk_resume_workflows

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

With no annotations, the description carries the full burden. It discloses the valid input states (CANCELLED, ENQUEUED), the effect on queue (bypass or enqueue via queue_name), and the return values. This goes beyond the bare mutation semantics and gives the agent a solid understanding of behavior.

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 efficiently structured with a one-sentence summary, a short behavioral paragraph, then clearly labeled 'Args' and 'Returns' sections. Every sentence earns its place, with no redundancy or fluff.

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?

The description fully explains the tool's purpose, target states, optional queue behavior, all parameters, and the return format. Given the tool's moderate complexity, this is complete and self-contained.

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 'Args' section adds meaning beyond the schema: it labels application_name as required, describes workflow_ids as 'IDs of the workflows to resume,' and for queue_name explains the behavioral consequence ('If provided, enqueue the resumed workflows onto this queue instead of running them immediately'). The schema itself provides only types and titles, so this is valuable.

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 opens with 'Resume multiple workflows at once,' which is a specific verb+resource statement. It further specifies the target states (CANCELLED and ENQUEUED), which distinguishes it from sibling tools like resume_workflow (singular) and bulk_cancel_workflows.

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 clear context on when to use the tool: 'Resumes execution of workflows that are in CANCELLED state' and 'You can also use this on workflows in ENQUEUED state to immediately start them, bypassing their queue.' While it doesn't explicitly mention alternatives like resume_workflow, the bulk nature and state-specific behavior imply the appropriate use case.

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