bulk_update_cases

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

Annotations already indicate the operation is mutable, destructive, and idempotent, so the description has limited burden. It adds the same-project constraint, but does not disclose partial-failure behavior, response shape, or whether tag operations merge or replace existing tags. That leaves some behavioral ambiguity for a bulk mutation 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?

Three short sentences, each carrying meaningful information: the action, the supported fields, and the project constraint. The description is front-loaded and contains no filler.

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?

The description covers the essential purpose, supported fields, batch scope, and the key constraint that all caseIds must belong to the same project. Since there is no output schema, it could ideally mention the response or partial failure semantics, but the current description is complete enough for a caller to select and invoke the tool correctly.

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?

The schema covers 100% of parameter descriptions, including caseIds constraints and the updates sub-fields. The description adds only the same-project constraint beyond what the schema says, so the baseline score of 3 is appropriate.

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 states a specific action and resource: 'Update multiple test cases at once' and enumerates exactly which fields can be changed (status, priority, tags). The 'at once' plus 'batch' framing also gives agents a clear signal how to distinguish this from the single-case sibling update_test_case.

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 gives clear context: this is for bulk updates and requires all cases in the same project. It doesn't explicitly state 'use update_test_case for a single case' or 'don't use for cross-project cases', but the same-project constraint and batch framing make the primary usage reasonably explicit.

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