Transition Jira issue

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

Annotations already disclose that this is a non-read-only, open-world, non-destructive mutation. The description adds useful behavioral context by requiring a currently available transition and a valid transition ID, though it does not explain side effects of fields/comment or what happens on invalid transitions.

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 short sentences, both earning their place. The core action is front-loaded and the prerequisite follows immediately with no filler.

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?

The description covers the essential workflow prerequisite but is thin for a mutation tool with four parameters, a nested fields object, and no output schema. It should say more about how fields and comment affect the transition, though annotations already carry the basic safety profile.

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%, so the description must carry parameter meaning. It only indirectly explains transitionId via the lookup instruction and does not explain the nested fields object, the comment parameter, or the role of issueKey, leaving most parameter semantics undocumented.

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 verb and resource: moving an issue through a workflow transition. It also implicitly distinguishes itself from jira_list_transitions by casting that sibling as the lookup step rather than the mutation step.

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?

It gives an explicit prerequisite: call jira_list_transitions first to obtain a valid transition ID. That is concrete when-to-use guidance and names the exact alternative/supporting tool an agent should use before invoking this one.

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