bulk_update_issues

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

Annotations already establish this is a non-read-only, non-destructive write, so the description's added burden is lighter. It usefully explains that values follow the issue edit format and that array fields support add/set/replace merge commands, but it stays silent on permissions, reversibility of overwrites, and what the call returns. Note the tension worth surfacing to the agent: the schema's confirm parameter calls this a 'destructive/bulk operation' while destructiveHint is false.

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?

Two sentences, front-loaded with the operation and its limit, followed by exactly one concrete syntax example. No filler, and the compact inline JSON example is the most efficient way to convey the command structure.

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 high-impact bulk mutation tool with nested objects and no output schema, the description covers scale and value syntax but omits what the agent gets back (a bulk operation id?), whether confirm=true is required to proceed, and what permission level is needed. The sibling get_bulk_operation_info hints at an async result the description never mentions.

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 a baseline of 3 applies, but the description goes beyond the schema by documenting merge semantics for array fields ('add'/'set'/'replace'), which the schema's generic 'Fields to set' wording does not convey. It does not elaborate on the issues/filter string or notify parameters, but those are already well covered in the schema.

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 edit many issues at once') plus a hard scope limit (max 10000), so an agent immediately knows this is a multi-issue write. It does not, however, distinguish itself from nearby siblings such as bulk_update_entities, bulk_move_issues, or bulk_transition_issues, leaving the agent to infer the boundary.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternative (single edit_issue, or the more specific bulk_move/bulk_transition tools). The only implicit signal is the bulk scope plus the 10000 cap, which is a constraint rather than routing guidance.

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