Delete a user

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

Annotations already flag destructive=true and idempotent=false, but the description goes well beyond them: permanence with no undo point, multisite limiting deletion to the current site, temporary admin-role removal with restoration on failure, partial-failure semantics (deleted + warning), and a concurrency lock with the caveat that wp-admin changes are not covered. This is unusually rich for a destructive operation.

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?

Front-loaded with the action and the reassign branch before edge cases, and nearly every clause carries operational information. It is a dense semicolon-chained paragraph, though, and the plugin-hook failure clause is hard to parse on first read.

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?

With no output schema, the description supplies the return values ("deleted and id"), and it covers permissions, multisite scope, role-restoration rollback, partial failure, and concurrency. An agent has everything needed to call it correctly or decide not to.

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 coverage is 100%, so the baseline is 3, and the description adds real meaning: it spells out exactly what happens to the deleted user's posts and links when reassign_to is omitted versus supplied, and notes that 0 is equivalent to omitted. Only the id format is left entirely to the schema.

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?

Opens with a specific verb and resource ("Delete a user account"), which cleanly separates it from the read/create/update siblings (wp_get_user, wp_create_user, wp_update_user, wp_list_users). The scope — full account removal, not just site membership — is stated explicitly.

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?

Gives concrete conditions for the two branches: supply reassign_to to hand content to another user, omit it to let WordPress trash/delete the authored content. It also states refusal cases (missing delete_users capability, last administrator, ab_mcp_busy, invalid reassign target). No sibling alternative is named, but there is no competing delete-user tool.

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