wp_add_user

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost nothing beyond 'this creates something'. It omits whether a password is generated when omitted, what a missing 'role' defaults to, whether a notification email is sent, whether the caller must be authenticated, and whether the operation fails on duplicate usernames.

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?

It is a single, front-loaded sentence with no wasted words, which is good structure. But for a six-parameter mutation tool the brevity is under-specification rather than genuine conciseness, so it cannot rate highly on this dimension.

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 annotations, no output schema, six undocumented parameters at 0% schema coverage, and only a five-word description, an agent lacks nearly everything needed to invoke this correctly. The definition is materially incomplete for the tool's complexity.

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 description coverage is 0% and the description names none of the six parameters. An agent gets no indication of accepted role values, email format requirements, password handling, or how first_name/last_name relate to the user record. Nothing compensates for the coverage gap.

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 states a specific verb and resource ('Add a new WordPress user'), making the operation immediately clear and distinguishable from siblings like wp_add_post or wp_add_page. It does not, however, differentiate from the adjacent wp_update_user / wp_delete_user lifecycle tools, so it stops short of the top mark.

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?

There is no guidance on when to use this tool versus wp_update_user or wp_users_search, nor any statement of prerequisites such as required capability or admin-level permissions. The agent must infer an appropriate calling context entirely from the tool name.

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