jira_transition_issue

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

The description claims support for adding a comment and setting resolution, but the input schema lacks parameters for these, creating uncertainty about actual behavior. No other behavioral traits are disclosed.

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 short and front-loaded, but the unsupported claim about comment/resolution wastes space and reduces conciseness.

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 absence of input parameters and output schema, the description does not fully clarify how to use the tool or what it returns, leaving significant gaps.

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?

With 0 parameters in the schema, the description mentions features that imply parameters (comment, resolution), but these are not defined, causing confusion and reducing value.

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 clearly states the tool transitions a Jira issue to a new workflow status with an example ('To Do' -> 'In Progress' -> 'Done'), differentiating it from siblings like jira_update_issue.

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 explicitly advises using jira_get_transitions first to discover available transitions, providing a clear prerequisite.

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