mcp_delete_user

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action ('delete a user and reassign their content') without explaining irreversibility, required permissions, or what happens to associated data (e.g., posts, comments). The description lacks sufficient transparency for a destructive tool.

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 extremely concise (one sentence, six words), front-loading the action. However, this conciseness comes at the cost of missing important details, such as behavioral transparency, making it slightly under-specified.

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 the lack of annotations and output schema, the description should provide more context about the tool's behavior, such as what 'content' includes, whether the action is reversible, and any side effects. The current description is insufficient for a complete understanding.

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 schema already documents both parameters. The description adds minimal extra meaning beyond confirming that content reassignment is part of the operation. Baseline 3 is appropriate as the description does not significantly enhance 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?

The description clearly states the verb ('delete a user') and the resource ('a user') with an additional detail ('reassign their content'), making the tool's purpose specific. However, it does not differentiate itself from the sibling tool 'wp_delete_user', which has the same verb and similar purpose.

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 implies when to use the tool (when deleting a user and wanting to reassign content) via the reassign parameter, but it does not explicitly state when not to use it or provide alternatives. The usage context is implied but not fully articulated.

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