batch_cancel

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

With no annotations, the description must disclose behavioral traits. It mentions concurrent processing and default concurrency, but fails to address important aspects like reversibility, partial failures, error handling, or side effects. The behavioral disclosure is minimal.

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 two sentences, front-loaded with the primary purpose, and no wasted words. It efficiently conveys the core functionality and key parameter.

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 of a batch operation with 3 parameters and no output schema or annotations, the description is too sparse. It omits return values, success/failure indicators, query format, and partial failure handling, leaving the agent underinformed.

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%, so baseline is 3. The description adds little beyond the schema, only citing 'concurrent processing for speed' which is not parameter-specific. It does not provide additional parameter meaning or usage examples.

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 it cancels multiple workflows matching a query with concurrent processing. It distinguishes itself from singular cancellation (cancel_workflow) and other batch operations like batch_terminate or batch_signal by specifying 'cancel' and 'concurrent processing for speed'.

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 cancelling multiple workflows matching a query, but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like individual cancellation or batch_terminate. No exclusions or contexts are mentioned.

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