transitionJiraIssue

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered externally. The description adds useful scope information beyond that — that a comment can be attached and that sprint/backlog assignment is a possible side effect — but says nothing about failure modes (invalid transition IDs), required permissions, or the fact that repeating the call is not idempotent.

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 that wastes no words. It loses a point for the grammatical slip ('an work item') and the ambiguous 'and/or', which forces the agent to guess whether both effects can occur in one call.

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 non-idempotent mutation with a nested free-form 'fields' object and no output schema, the description is thin: it never explains what 'fields' expects or how resolution-style objects tie into the status change. Annotations cover the safety profile and the schema covers most parameters, so it is minimally viable 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?

Schema description coverage is 75%, with comments on 'transitionId' (pointing at listJiraIssueTransitions) and 'comment' and a bare-bones 'fields' placeholder. The description itself adds no parameter meaning at all — it never mentions transitionId, fields, or comment — so it does not compensate for the one undocumented parameter (issueIdOrKey). Baseline 3 applies when the schema does most of the work.

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 gives a specific verb and resource ('Transition an work item to a new status') plus a secondary capability ('assign it to a sprint or backlog'), so an agent understands the operation. It does not, however, differentiate itself from the closely related editJiraIssue sibling, which could also change status-like fields.

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 when-to-use guidance, no mention that listJiraIssueTransitions must be called first to obtain a valid transitionId (that hint lives only in the parameter schema), and no statement of when to prefer this over editJiraIssue. Usage is left entirely to inference.

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