wp_create_user

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

The description transparently discloses important behavioral details: the password is never echoed back and must be recorded beforehand, dry_run creates nothing by default, and the tool requires specific credentials and flags. This fully informs the agent about side effects and preconditions.

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 somewhat long but every sentence adds valuable information. It is well-structured with clear emphasis on critical warnings. No filler or redundancy, though it could be slightly trimmed without loss of meaning.

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?

The description provides good safety and requirement context, but it lacks details about the 'install' parameter and does not mention what the tool returns (e.g., user ID or success object). Given the absence of an output schema and annotations, these gaps reduce completeness for an agent deciding to call it.

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 description explains the semantics for username, email, roles, password, dry_run, and allow_prod, but omits two parameters: 'name' (likely a display name) and the required 'install' parameter, which specifies the target WordPress installation. This is a significant gap since 'install' is required and not mentioned at all.

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 tool's purpose: creating a WordPress user with role and password. It uses a specific verb and resource, and the context distinguishes it from siblings like wp_update_user, wp_delete_user, and wp_list_users.

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 gives explicit usage instructions: dry_run defaults to true and must be set to false to actually create, prod writes require allow_prod=true, and it requires REST transport and an administrator app password. This provides clear guidance on when and how to use the tool.

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