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 behavioral burden. It usefully discloses the side effect that a comment may be posted, but says nothing about required permissions, that transitionName must match an actual workflow transition, or what happens on an invalid transition.

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 sentences, no filler, purpose and optional side-effect front-loaded. Every clause earns its place.

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?

With no annotations and no output schema, the description covers the core purpose and the comment side effect, but leaves the agent without permission prerequisites, workflow-validation behavior, or any indication of the result. Adequate but visibly incomplete for a mutation tool.

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 67%; transitionName is well documented in the schema and the description reinforces the 'as shown in Jira workflow' nuance. issueKey is undocumented in both places, and the description adds no format detail beyond the schema.

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 a specific verb ('Transition') and resource ('a Jira issue') with a target ('a new status') and concrete examples. It is distinguishable from jira_update_issue in principle because it names status transition rather than field editing, though it never explicitly says so.

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 on when to use this versus jira_update_issue or jira_add_comment, even though both overlap (status change vs field update; the optional comment vs the dedicated comment tool). Usage is only implied by the verb choice.

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