transition_issue

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

Discloses the dual mode (list/execute) and resolution requirement, but does not mention side effects (e.g., notifications, irreversibility) or behavior when issue is already in target state. Without annotations, more detail would be beneficial.

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?

Three sentences, front-loaded with main action, no fluff. Every sentence provides essential information.

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?

No output schema; description does not explain return values after executing a transition. Could elaborate on allowed resolution values or error conditions. Adequate but not complete.

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?

Adds value beyond the schema by explaining the relationship between transitionId and transitionName and the purpose of listTransitions. Schema coverage is 100%, so baseline 3 plus extra context.

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?

Clearly states it transitions an issue through its workflow, with the ability to execute by name/ID or list transitions. Distinguishes from sibling tools like update_issue (field modification) and create_issue (creation).

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?

Provides guidance to use listTransitions=true before attempting a transition and notes that some transitions require a resolution. Lacks explicit comparison to alternatives or when not to use.

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