jira_transition

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

No annotations provided, so description carries the full burden. It discloses that transition matching is case-insensitive, that list=true returns YAML with id/name pairs, and that comment is posted after success. However, it does not discuss required authentication, permissions, or rate limits, which are relevant 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?

Single paragraph, entirely on-topic, no redundant sentences. Each sentence adds useful information: purpose, usage, matching behavior, listing fallback, and optional comment. Perfectly concise.

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 moderate complexity and full schema coverage, the description is mostly complete. It explains the listing mode's output format. However, it does not describe the success response for a normal transition (e.g., returned issue), which is minor but notable.

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 coverage is 100% but description adds significant value: it explains that transition can be name or id (case-insensitive), that list=true changes behavior to listing, and that comment is optional and added after the transition. This goes beyond the schema's basic 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?

The description clearly states the tool's purpose: 'Transition a JIRA issue to a new workflow status.' It includes specific usage examples and distinguishes itself from the sibling jira_transition_list tool by also handling the listing functionality via the 'list' parameter.

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 explicit guidance: explains how to pass transition name or id, mentions case-insensitive matching, and instructs to call with list=true if unsure of valid transitions. It also notes that comment is optional and posted after transition.

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