jira_transition_issue

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does reveal that the operation is a mutation and names the mechanism (workflow transition), but it does not mention that valid transitions depend on the issue's current status or what error/response behavior to expect.

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?

A single sentence communicates the action, mechanism, and examples, with no filler or repetition. The core purpose is front-loaded and immediately usable by an agent.

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 simple tool with two fully documented required parameters, the description covers the essential operation well. Missing details like response format and workflow-availability constraints are minor, and the tool remains invokable from the description plus schema alone.

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?

The schema already documents both parameters with 100% coverage, so the baseline is 3. The description adds some context by tying transitionName to a new status, but it mostly reinforces the schema's own param descriptions rather than providing deeper semantic detail.

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?

The description states a specific action ('Move a Jira issue to a new status') and the mechanism ('triggering a workflow transition'), with concrete examples. This clearly distinguishes the tool from siblings like jira_update_issue, which handles field updates rather than status changes.

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?

No explicit guidance is given about when to use this tool versus alternatives, nor when not to use it. The intended use is implied by the wording, but the agent is not told to prefer this over jira_update_issue for status changes or warned that only currently available workflow transitions can be applied.

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