Transition Workflow Node

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

The description adds important behavioral context beyond the annotations by stating 'Defaults to dry-run for safety.' This discloses a safety mechanism not captured by destructiveHint or openWorldHint, helping the agent understand that the tool does not make changes by default. It does not contradict the annotations, and while it does not fully enumerate all side effects, the dry-run default is a significant behavioral disclosure.

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, using a single sentence with no filler words. It front-loads the purpose and includes a key safety note. However, its brevity verges on under-specification, leaving out critical details; still, as far as conciseness alone, it is efficient and well-structured.

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 complexity (7 parameters, destructive nature, open-world hint, no output schema), the description is insufficiently complete. It does not explain what a 'workflow node' is, how transition differs from rollback, nor what outputs or errors to expect. The one-sentence description leaves significant gaps that the schema and annotations only partially fill, making it unlikely an agent could invoke this tool correctly without additional context.

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 must compensate for parameter details, but it does not. The only parameter-related hint is 'Transition or rollback,' which vaguely suggests the 'action' parameter but does not explain node_id, node_ids, project_key, rollback_reason, or dry_run semantics. The description lacks the depth needed to compensate for the schema's minimal documentation.

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 verb and resource: 'Transition or rollback a workflow node.' This conveys the core action without excessive ambiguity. However, it does not explicitly distinguish this from sibling tools like workflow_transition_state or workflow_smart_transition, which likely perform similar operations; the focus on 'node' provides some differentiation but not a clear contrast.

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 offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or exclusions. The only hint is 'Defaults to dry-run for safety,' which implies a cautious approach but does not clarify use cases or contrast with sibling tools.

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