Transition Jira Issue

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

With no annotations, the description has the full burden of disclosing behavioral traits. It only states that the issue is moved to another workflow state, without mentioning side effects, permissions, or failure modes (e.g., invalid transitionId). This is insufficient for a state-changing tool.

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 concise sentence with no unnecessary words, front-loading the core action. It is slightly too sparse, but this is more a completeness issue than a conciseness issue, so the structure itself earns a 4.

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 mutation tool with no annotations, no output schema, and minimal parameter info, the one-sentence description is inadequate. It does not explain how to discover valid transition IDs, what happens after the transition, or whether the change is reversible. The absence of response details leaves the agent with an incomplete picture.

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 does not compensate by explaining that issueKey identifies the issue and transitionId is a workflow transition identifier. While the parameter names hint at their meaning, the description adds no meaningful detail beyond the raw schema 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 uses a specific verb ('move') and resource ('issue') with a target ('another workflow state'), making the action clear. It implicitly distinguishes from siblings like jira_create_issue or jira_search, but does not explicitly name alternatives, so it falls short of 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?

There is no guidance on when to use this tool versus alternatives such as jira_assign_issue or jira_create_issue. It also does not explain how to obtain a valid transitionId or the context in which transitions apply, leaving the agent without usage direction.

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