batch_cancel_activities

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

With no annotations, the description must disclose all behavioral traits. It mentions concurrent processing and the concurrency parameter, but fails to describe side effects, return values, error handling, or authorization requirements for this destructive batch operation.

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?

Two sentences with no wasted words. The first sentence states purpose and key feature (concurrent), the second provides a parameter hint. Front-loaded and efficient.

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 (batch operation with multiple siblings, no output schema), the description omits important details like return format, error behavior, and selection criteria beyond 'matching a query'. Agents lack context for correct invocation among many similar tools.

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 the baseline is 3. The description adds minimal extra meaning: it highlights 'concurrent processing' and mentions the concurrency default (already in schema), and introduces 'standalone' context not in schema, but lacks depth.

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 selection method ('matching a query'). It differentiates from single-activity tools like 'cancel_activity' but could more explicitly distinguish from sibling batch tools like 'batch_terminate_activities'.

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?

No guidance is given on when to use this tool versus alternatives. There are many sibling batch tools (e.g., 'batch_cancel', 'batch_terminate_activities') but no mention of when one is preferred or what 'standalone activities' means versus other types of activities.

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