Delete a user

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

The description goes well beyond the annotations by disclosing that WordPress has no trash for users, making deletion permanent and irreversible, requiring confirm: true, and explaining the content handling options (reassign vs delete). This adds significant behavioral context about consequences and prerequisites, enriching the annotation hints (destructiveHint=true) without contradiction.

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 concise—two sentences that directly state the purpose, permanence, confirm requirement, and content handling, with the most critical behavioral note front-loaded. There is no redundant information or fluff; every sentence earns its place.

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 destructive mutation with complex content handling, the description covers all essential aspects: irreversibility, confirm requirement, content reassignment vs deletion, and how site selection works. The absence of an output schema is acceptable as the description focuses on the action and its consequences, which is sufficient for an agent to correctly invoke the 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?

While the schema has 100% coverage, the description adds meaningful semantic context: confirm is emphasized as 'Required — user deletion cannot be undone' and reassign_to is clarified as 'User ID to inherit this user's posts' with guidance on omitting it only if content should be deleted. The site_id behavior is also explained, providing value beyond the bare 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 begins with 'Delete a user' and immediately clarifies the permanent nature and the confirm requirement, distinguishing it from user creation/updating. It explicitly states the resource (user) and the action (delete), making it unmistakable and clearly differentiated from siblings like update_user and create_user.

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 explains when to use the tool (when deleting a user is required) and what must be done: require confirm: true, and choose whether to reassign content or delete it. It also provides guidance on the site_id parameter (optional, default site behavior) and the need to run list_sites for valid ids, offering clear context for appropriate use.

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