transition_role_workflow

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It's a state-changing operation (transition) but provides no detail about side effects: what happens to the current role's state, whether the transition is reversible, whether handoffNotes are stored/visible, or what happens if transition fails. For a mutation tool with zero annotation coverage, this is a significant gap.

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 a single efficient sentence with no waste. It gets to the point quickly. Slightly more could be added given the tool's complexity, but there are no redundant phrases or filler.

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 workflow-transition tool with 5 parameters including ambiguously overlapping fields (rationale vs handoffNotes), no output schema, and no annotations, the description is inadequate. It should clarify expected values for 'toRole', the behavioral consequences of a transition, and how it relates to the nearly identical sibling 'transition_role'. The description leaves too much to the agent's inference.

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%, so the schema already documents all 5 parameters. The description adds no parameter-level meaning beyond what the schema provides — it doesn't clarify the distinction between 'rationale' and 'handoffNotes' (both sound similar), nor what format 'toRole' expects or what 'decisions' items should contain. Baseline 3 applies when schema carries the load, but no extra value is added.

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 'Transition to a different role in the workflow execution' is a clear verb+resource statement conveying the core purpose. However, it doesn't distinguish from the sibling tool 'transition_role' which appears to be a near-duplicate — the relationship between the two is entirely unexplained, so an agent cannot tell which to use.

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?

No when-to-use guidance, no exclusions, and no differentiation from the sibling 'transition_role' tool. The description gives no context about when this workflow-level transition is preferred, what prerequisites exist (e.g., must the workflow be running?), or what role names are valid.

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