list_ticket_transitions

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

With no annotations, the description carries the full burden, and 'list all available' does convey a non-mutating read operation. It does not disclose permission requirements, rate limits, or anything about the shape/ordering of returned transitions, so behavioral disclosure is only partial.

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?

One tight sentence with the resource and scope front-loaded and zero filler. Slight redundancy between 'available' and 'allowable state changes' keeps it from being maximally economical.

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 single-parameter read tool with no output schema, the description covers the essential purpose and scope; nothing critical to invoking it correctly is missing. Additional detail on the returned transition structure would be a bonus rather than a requirement here.

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 100% and the single issue_key parameter is documented with a format example, so the schema does the heavy lifting. The description adds only that the key refers to a 'Jira ticket', which is baseline-level 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?

States a specific verb (list) and resource (workflow transitions) scoped to a Jira ticket, and clarifies the intent ('to check allowable state changes'). It implies a read-only inspection role distinct from the mutating transition_jira_ticket sibling, but never names that sibling explicitly, so an agent must infer the split.

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 phrase 'to check allowable state changes' implies the tool is a pre-flight lookup before performing a transition, which is useful context. However, it gives no explicit when-to-use condition or pointer to transition_jira_ticket as the follow-up action.

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