Bulk create test cases

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

The description discloses atomicity ('batch is validated as a whole, so an invalid item means nothing is created'), return behavior ('Returns the IDs in the order submitted'), and performance characteristics ('four times faster and one tenth of the calls'). These go well beyond the annotations, which only indicate openWorldHint and non-destructive behavior.

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 dense but every sentence earns its place: it front-loads the core purpose and sibling distinction, then explains batch behavior, return format, and performance. The structure flows logically from what to use, to how it behaves, to cost/benefit. 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?

Given the tool's complexity (nested steps, multiple enum fields, shared steps), the description covers the essential behavioral aspects that an agent must know: atomicity, return order, and the relationship to qase_case_upsert for field semantics. It also covers the performance consideration for deciding between batch and individual calls. Nothing critical is missing for correct invocation.

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 meaningful context beyond the schema: it clarifies enum handling ('labels ("high", "blocker") or numeric IDs both work'), steps formats ('steps classic or Gherkin'), and the atomicity of the `cases` parameter. This enhances understanding of how parameters behave, moving beyond the schema's field-level descriptions.

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?

Clearly states the tool creates up to 100 test cases in one request and explicitly positions itself as the batch form of qase_case_upsert. The verb and resource are specific, and the description immediately distinguishes it from the sibling tool, making purpose unambiguous.

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?

Explicitly states when to use it: 'the right tool whenever more than one case is being written.' Also provides exclusion guidance: 'This creates only; to change an existing case use qase_case_upsert with its `id`.' Additionally advises splitting larger imports across multiple calls, covering both when and when-not scenarios.

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