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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), so the description is not carrying that burden. It nonetheless adds a genuinely useful behavioral claim beyond the structured data: all changes apply 'in one atomic operation', telling the agent the batch is all-or-nothing rather than partially applied.

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, no filler, with the core action and the 50-item limit front-loaded and the field list following. Nothing is repeated and nothing extraneous is included.

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 bulk mutation with no output schema and a nested patch object, the atomicity disclosure is the most important inclusion and it is present. Still missing: what the response reports (per-issue success/failure, count), and the cross-issue constraint implied by the state field being resolved on a single team.

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 50% and the mutating surface is a nested 'patch' object, but each nested field already carries its own schema description (including the crucial 'labels replaces the labels already on the issue' and the null-to-remove semantics). The description's field list largely restates the schema, though the 'sprint (cycle)' mapping adds mild orientation value.

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 concrete verb and resource ('Update multiple issues at once'), scopes it ('up to 50'), and enumerates the mutable fields (state, assignee, labels, priority, sprint/cycle, project). The plural 'multiple issues' cleanly separates it from the sibling update_issue without needing to name it.

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 batch framing implies when to prefer this over single-issue updates, and the 50-item ceiling sets a practical bound. However, there is no explicit when-not guidance, no mention of prerequisites (e.g. all issues sharing a team, since state is resolved 'on the issues team'), and no pointer to update_issue for single-item edits.

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