batch_cancel

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

With no annotations, the description carries the full burden. It discloses that cancellation is concurrent and uses a query, but it does not detail side effects (e.g., whether workflows are hard-terminated), error handling, or return values. The concurrent processing note adds some value beyond the schema.

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 only two sentences, concise and front-loaded with the core purpose. Every sentence adds value, with no redundant or filler content.

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 batch operation complexity and lack of output schema, the description omits crucial details such as return values (e.g., number of canceled workflows), error behavior, and idempotency. It does not fully compensate for missing structured information, leaving gaps for an agent.

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?

All three parameters have complete schema descriptions (100% coverage), so the baseline is 3. The description merely restates the concurrency parameter's default, adding no new semantic meaning beyond what the schema already provides.

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 cancels multiple workflows matching a query, with concurrent processing. The verb 'cancel' and resource 'multiple workflows' are specific, and the tool is distinguished from siblings like 'cancel_workflow' (single) and 'batch_cancel_activities' (different resource).

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 implies usage for canceling workflows and mentions concurrency control, but it does not provide explicit guidance on when to use this tool versus alternatives like 'batch_signal' or 'batch_terminate'. No exclusions or prerequisites are stated, leaving the agent to infer context from the tool name.

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