moderation_state_deleteDeletes a Drupal moderation state using its state_id to remove unused workflow states and maintain accurate content moderation settings.
Delete a moderation state.
| Name | Required | Description | Default |
|---|---|---|---|
| state_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only says 'Delete' without disclosing required permissions, irreversibility, effects on content using the state, or whether deletion is blocked when the state is in use.
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 short sentence with no wasted words and the action is front-loaded. However, it is under-specified for a destructive tool, making its brevity more a gap than an efficiency win.
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 that this is a destructive operation, there are no annotations, schema coverage is 0%, and many sibling tools exist, the description omits critical context such as prerequisites, side effects, permission requirements, and failure conditions. The output schema exists, so return values need not be covered, but the behavioral context is substantially incomplete.
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% and the description provides no meaning for state_id beyond its name. It does not explain whether this is a numeric ID, machine name, or UUID, nor any format or lookup expectations.
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 states a specific verb ('Delete') and resource ('moderation state'), so the action is clear. However, it does not differentiate this tool from siblings such as moderation_state_list, moderation_state_get, moderation_state_update, or moderation_transition_delete, and it essentially restates the title.
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 guidance is given about when to use this tool versus alternatives, nor are prerequisites or exclusions mentioned. The description provides no context for choosing moderation_state_delete over other moderation-state or transition operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.