jira_transition_issue

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a mutation via POST but does not disclose that transitions may require additional fields, may be irreversible, depend on the issue's current workflow state, or require specific permissions.

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?

The description is a single efficient sentence with no filler and the endpoint is included for precision. It is concise, though the brevity comes at the cost of behavioral and parameter detail.

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 tool with no annotations, no output schema, and no schema descriptions, this description is too sparse. It does not explain how to construct the fields object, whether the transition can change required fields, or how the tool relates to jira_get_transitions, leaving important operational knowledge implicit.

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 0%, and the description adds no parameter-level meaning. While issueIdOrKey and transitionId are reasonably self-explanatory, the 'fields' and 'comment' parameters remain underspecified—especially 'fields', which often carries required transition fields.

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 ('Applies a transition') and identifies the REST endpoint, making it clear this tool performs a state transition on a Jira issue. It is distinguishable from sibling tools like jira_get_transitions by its verb and POST method, though it does not explicitly name the alternative.

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 guidance is provided about when to use this tool versus related tools such as jira_get_transitions or jira_edit_issue. The description does not mention prerequisites like retrieving valid transition IDs first, nor does it describe any exclusions.

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