Transition Workflow State

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable behavioral context by stating the default is a dry-run, meaning the tool does not mutate by default. However, it does not disclose what happens when dry_run is false or the likely side effects of a real transition.

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?

The description is extremely concise: two short sentences, front-loaded with the core verb and resource, followed by an important safety note. No unnecessary words.

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 destructive, potentially mutating operation with four parameters and no output schema, this description is too sparse. It lacks context about real transition behavior, return values, error handling, and how to use the tool correctly beyond the dry-run default. The wide set of sibling workflow tools increases the need for clearer contextual guidance.

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?

The input schema has 0% description coverage for its 4 parameters, and the description fails to compensate. It references 'dry-run' generically but does not explain work_item_id, transition_id, project_key, or the exact meaning/effect of the dry_run parameter beyond its default.

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 identifies the action ('Transition') and the resource ('state-flow status'), making the basic purpose understandable. However, it does not distinguish this tool from closely related siblings like workflow_transition or workflow_smart_transition.

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 description mentions 'Defaults to dry-run for safety,' which implies a safe-use context, but it gives no explicit guidance on when to choose this tool over alternatives or what prerequisites are needed. There is no discussion of when a real (non-dry-run) transition is appropriate.

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