batch_cancel_activities

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

No annotations are provided, so the description must carry the burden. It discloses concurrent processing and the concurrency parameter, but fails to mention important behaviors such as partial success handling, idempotency, error states, or whether the operation is reversible. The description is adequate but not comprehensive.

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 long, front-loading the purpose and adding the key concurrency detail without extraneous words. Every sentence earns its place.

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 lack of output schema, the description should hint at return values or results (e.g., count of cancelled activities). It also omits behavior on errors, partial success, and concurrency limits. The sibling set is large, so more differentiation would help. The description is functional but incomplete for full agent understanding.

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 description coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema: it repeats the concurrency default and emphasizes parallelism. It does not explain the query parameter further or clarify the limit parameter's behavior (e.g., what happens when reached).

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 action ('Cancel'), resource ('multiple standalone activities'), and key method ('matching a query with concurrent processing'). It differentiates from sibling tools like cancel_activity (single) and batch_cancel (likely for workflows) by specifying 'standalone activities' and concurrent processing.

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 use when canceling many activities at once, but does not explicitly state when not to use it or compare with siblings like batch_terminate_activities or cancel_activity. No guidance on prerequisites or context is provided.

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