Moderation Transition Delete

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

With no annotations, the description carries the behavioral burden and does well: it states that the transition is configuration inside its workflow, that deletion goes through `WorkflowTypeInterface::deleteTransition()` and saves the workflow, and that the reply reports the remaining transition count while warning if the last transition was removed. It does not disclose permission requirements, reversibility, or error cases, so it stops short of full transparency.

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 front-loaded with the core action and then adds useful context in two short paragraphs. Most sentences earn their place, though the reference to Drupal's own delete form and the backtick-quoted method name add minor verbosity rather than essential information.

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 two-parameter mutation with no annotations and an output schema that covers return values, the description supplies key behavioral context: workflow side effect, return summary, and the warning when no transitions remain. It remains incomplete on parameter semantics and permission prerequisites, but the output schema reduces the need to explain return values.

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 both parameters, but it only refers to 'a workflow' and 'a transition' generically. It offers no explanation of what `workflow_id` and `transition_id` are (e.g., machine names), their format, or how to discover valid values, leaving the parameters largely undocumented.

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 first sentence states a specific verb and resource ('Delete a moderation transition from a workflow') and the description explicitly frames it as the counterpart of `moderation_transition_create`. This distinguishes the tool from sibling create/get/list operations without requiring the schema to be opened.

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 clarifies that this is the delete counterpart to `moderation_transition_create`, giving clear context for when to use it versus the create tool. It does not provide explicit when-not-to-use exclusions or mention other alternatives such as listing or inspecting transitions first, keeping it from a top score.

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