update_cases

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is largely covered structurally. The description adds the prerequisite lookup step, but much of that same detail (system_name requirement, merge-into-root behavior, error on unknown field names) is duplicated in the schema rather than delivering new behavioral context. It never addresses what happens to fields not included in the update or whether a partial failure leaves cases half-updated.

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, front-loaded with the action and scope, then prerequisite, then efficiency rationale. Each sentence earns its place, though the get_case_fields prerequisite is repeated verbatim in the schema's field description.

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 two-parameter bulk mutation with full schema coverage and annotation coverage, the description supplies the operational context an agent needs: valid field names come from get_case_fields and bulk is preferred over repeated single updates. The remaining gap is batch semantics (all-or-nothing vs partial success), which no output schema exists to cover.

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% and the nested 'fields' object is thoroughly documented with examples, valid-name rules, and API merge semantics. The description adds no parameter-level information beyond what the schema already states, so the baseline 3 applies.

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 update multiple test cases') plus the key constraint that all cases receive the same field values. It also explicitly names the sibling it supersedes ('update_case'), so an agent can route between them without opening schemas.

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 alternative ('More efficient than calling update_case multiple times') and a hard prerequisite ('requires knowing valid field names that are returned by get_case_fields'). It stops short of explicit when-not guidance, e.g. whether single-case edits should still use update_case, but the selection context is easy to infer.

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