wordpress_delete_userDelete a WordPress user and reassign their posts and content to another user. Prevent data loss by transferring ownership before removal.
Delete a user (reassign their content to another user)
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | ||
| reassign | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. It does reveal a key side effect (content reassignment), which is valuable. However, it omits critical safety information such as irreversibility, permission requirements, or effects on other user-related data.
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 that front-loads the action. There is no filler or redundancy. Every word adds value.
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?
Despite the low parameter count, this is a destructive operation with no annotations or output schema. The description does not mention irreversibility, prerequisites (e.g., the reassign user must exist), or error behavior. It captures the core action but lacks essential context for safe invocation.
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 schema only lists two number parameters. The description hints at the meaning of 'reassign' ('to another user') but does not explain 'userId' or explicitly map each parameter to its role. The description only partially compensates for the missing schema descriptions.
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 action ('Delete a user') and the resource (user). The parenthetical about reassigning content distinguishes it from simple deletion and aligns with the sibling tools (e.g., create_user, update_user). It is specific and unambiguous.
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 explicit guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparison to similar tools like wordpress_assign_role or wordpress_update_user. The description only implies deletion usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.