Delete WordPress User

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

Beyond the destructiveHint annotation, the description discloses that content is transferred to the reassign user, that WP REST does not support trashing, and that deletion is permanent. It also specifies the return format, providing valuable behavioral context.

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 well-structured with sections for overview, arguments, and return value. It is front-loaded with the purpose and remains compact, though the argument list is somewhat redundant with the schema.

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?

Since there is no output schema, the description provides the return shape ({ deleted: true, previous: <full user object> }) and explains the critical reassign behavior. It covers all essential aspects for correct invocation, making it complete for a mutation tool.

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?

The schema already provides 100% coverage for all 3 parameters with detailed descriptions, including the required reassign behavior. The description repeats this information without adding new semantics, so the baseline score of 3 applies.

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 'Permanently delete a user' with a specific verb and resource. It distinguishes this from sibling delete tools by noting WP REST does not support trashing, making this the definitive user deletion tool.

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?

It explicitly states that a reassign target is required and that deletion is always permanent, indicating when this tool should be used (when permanent removal is intended). However, it does not explicitly mention alternatives or when not to use it, though such cases may be rare.

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