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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is known. The description usefully adds that the batch is atomic and capped at 50, but says nothing about partial-failure behavior, required permissions, or that labels are replaced wholesale rather than merged (that detail lives only in the schema).

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 tight sentences, front-loaded with the batch scope and cap before the field list. The field enumeration is mildly redundant with the schema but earns its place as the only summary of the patch surface.

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 non-idempotent bulk mutation with a nested patch object and no output schema, the definition covers scope and atomicity but omits error/rollback semantics and what the call returns. Adequate to invoke correctly, incomplete for predicting outcomes.

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?

With only 50% schema description coverage, the description compensates by enumerating the patch keys (state, assignee, labels, priority, sprint/cycle, project), telling the agent exactly what can change in one call. It adds the 'sprint (cycle)' alias mapping, though it leaves null-to-remove and identifier formats to 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 ('Update multiple issues at once') plus the editable field set and the batch cap of 50. The word 'multiple' and 'across all issues' distinguishes it cleanly from the single-issue sibling update_issue.

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 it over update_issue, but the description never names that alternative or states a when-not condition (e.g., use update_issue for a single issue, or split batches above 50). Usage is inferable rather than prescribed.

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