listJiraIssueTransitions

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing on top of that: no note that it returns only transitions currently valid for the issue's present status, no permission requirements, no ordering guarantees.

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?

A single front-loaded sentence with no filler or redundancy; nothing could be cut. It is concise to a fault rather than verbose, so the shortness is under-specification rather than a structural flaw.

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 one-parameter read tool with annotations covering safety, the description is minimally adequate, and it does at least say what is returned (available transitions). But with no output schema, it should say that the result feeds transitionJiraIssue and what identifiers the transitions carry — the one piece of context an agent actually needs.

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 description carries the full burden for the single issueIdOrKey parameter. 'For a Jira work item' hints at what the parameter identifies but never states that it accepts either a numeric ID or a project key, or the format/constraints of either.

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 phrase 'Available workflow transitions for a Jira work item' names a specific resource (workflow transitions) scoped to a specific entity (a Jira work item), and the tool name supplies the 'list' verb. It is clear what the call retrieves, but it does nothing to distinguish itself from the sibling transitionJiraIssue, which is the natural confusion pair.

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?

There is no guidance on when to call this versus transitionJiraIssue, nor any stated prerequisite (e.g. call this first to discover valid transition IDs, then apply one). The one sentence is purely descriptive and leaves the agent to infer usage from the name alone.

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