Bulk create case reviews

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

Annotations only declare destructiveHint=false. The description adds real behavioral context beyond that: the one-API-call cost model regardless of batch size, and the API's lack of approve/merge/decline endpoints. It doesn't restate the atomic all-or-nothing validation (that lives in the schema), so it complements rather than duplicates structured data.

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?

A single tight paragraph with the core purpose and sibling relationship front-loaded. Every clause carries information; density is high but not padded.

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?

For a mutation tool with no output schema, it covers cost, field inheritance from the single-create sibling, and API limitations. It leaves return-value/reporting format and permission requirements implicit, which is a minor gap rather than a blocking one.

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 the schema already documents both parameters thoroughly. The description's only added semantics is the case_id edit-vs-create distinction, which the schema also states ('Omit for a new-case draft'). Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb and resource (bulk create case reviews) and explicitly frames itself as 'the batch form of qase_review_create.' An agent can distinguish it from the single-create sibling without opening either schema.

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?

Gives a clear selecting condition ('for proposing more than one change') and routes to alternatives: qase_review_create for the single case and qase_review_list to read status. It also rules out approving/merging/declining as UI-only. No explicit when-not-to-use beyond the batch-size condition, but coverage is strong.

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