jira_transition_issue

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds the mock-workflow status list, which is useful context, but says nothing about the consequence of a transition (the prior status being replaced, reversibility, or any permission requirements) for a tool flagged destructive.

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, front-loaded with the action and followed by the constrained value set. No filler or 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?

For a simple two-parameter mock tool with no output schema, the description covers the operation and the valid status domain; mutation semantics are largely carried by the annotations. Only minor gaps remain around permissions and reversibility.

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 schema alone only exposes a regex pattern for each argument. The description partially compensates by naming the four valid status values, which is genuine added meaning over the pattern, but it says nothing about the issue_key format or behavior.

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 and resource ('Move a Jira issue to a status') and enumerates the valid target statuses, so an agent knows exactly what the tool accomplishes. It doesn't explicitly name sibling tools, but the verb+resource pair is distinct enough from jira_create_issue and jira_search_issues that differentiation is implicit.

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?

The description implies when to use it (an issue needs a status change) and usefully constrains the status value set to 'Open, In Progress, In Review, Done'. However, it offers no explicit when/when-not guidance, no prerequisites, and no routing away from alternatives like jira_create_issue.

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