bulk_transition_issues

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description adds genuinely useful non-schema context: the dependency on get_issue_transitions and the resolution requirement for 'closed' transitions. It omits operational caveats such as the async/bulk-tracking behavior (get_bulk_operation_info) and the 10,000-issue cap, which live 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?

Three tight sentences, front-loaded with the core action, each adding a distinct actionable fact (mechanism, prerequisite tool, edge-case requirement). No filler or restatement of the tool name.

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 5-parameter bulk mutation with nested objects and no output schema, the description covers the key gotchas (transition ids, resolution requirement). It is only slightly incomplete in not signaling that this is a large-scale operation worth tracking via get_bulk_operation_info.

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 100% schema coverage the baseline is 3, but the description adds meaning beyond the schema by explaining that statuses like 'closed' may require a 'resolution' entry in values and that transition ids come from get_issue_transitions. It does not document notify, confirm, or the filter-string form of issues, which the schema already covers.

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+resource+mechanism ('Bulk move issues to a new status via a workflow transition'), which distinguishes it from single-issue execute_transition. It does not explicitly distinguish itself from the sibling bulk_move_issues or bulk_update_issues, so the agent must infer the difference, keeping it below a 5.

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 prerequisite/navigation hint ('Get available transition ids via get_issue_transitions') and a conditional rule about resolution for closed statuses. It stops short of naming when NOT to use this versus bulk_move_issues or execute_transition, so no explicit exclusion is provided.

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