jira_transition_issue

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

No annotations provided, so the description must disclose behavior. It explicitly mentions the state change and return confirmation, and points out the source of valid transition IDs. However, it omits permissions, failure modes, or reversibility, leaving some burden unmet for a mutation 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?

Well-structured with Args and Returns sections. Slightly longer than minimal but every sentence adds necessary information; no redundancy.

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?

Given the tool's low complexity and no output schema, the description provides the essential steps: how to obtain the transition ID and what is returned. It is complete enough for correct invocation, though it could mention error conditions.

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 has 0% description coverage. Description defines each parameter with examples (issue_key) and explains that transition_id comes from jira_get_issue transitions, and comment is optional. Fully compensates for schema's lack of descriptions.

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 'Transition a JIRA issue to a new workflow state' – clear verb, resource, target. Distinct from siblings (get, create, update) and references jira_get_issue for transition IDs.

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?

Explicitly directs to 'Use jira_get_issue with include_transitions=True to see available transitions and their IDs', giving a concrete prerequisite and pointing to the correct sibling tool. Clarifies when to use this tool.

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