Cancel Batch Task Group

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds valuable context: 'Writes a cancellation request that the detached group coordinator handles safely' – this explains that cancellation is asynchronous and not immediate, which is critical behavioral detail not in annotations. No contradictions with annotations.

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?

Three sentences, all essential: action, mechanism, usage context. No wasted words. Could be slightly more concise by merging first two sentences, but overall excellent structure and front-loading.

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 (2 parameters, output schema present), the description covers the core behavior and usage context well. It does not explain the output schema content or return values, but since an output schema exists, the description does not need to. The lack of details on edge cases (e.g., if group already done) is a minor gap.

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% (both parameters have descriptions). The description does not elaborate on parameter details beyond what the schema already provides. With full coverage, baseline 3 is appropriate as the description adds no extra parameter meaning.

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 'immediate cancellation of a running batch task group and its child tasks'. It uses specific verbs ('cancel', 'stop') and resources ('batch task group', 'child tasks'), and distinguishes from siblings by referring to a 'group' context, which the sibling list includes 'omp_cancel' (likely single-task cancellation).

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 explicit guidance: 'Call this immediately when the user asks to stop a batch.' This sets clear when-to-use context. However, it does not mention when NOT to use it (e.g., if the group is already finished) or alternatives among siblings like 'omp_cancel' for single tasks.

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