wp_create_user

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose an important safety behavior: safe mode requires confirm:true, and administrator role requires explicit confirm. However, it does not disclose side effects, permissions, email notifications, password generation behavior, or response format, leaving significant behavioral context unstated.

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 highly concise: two sentences, front-loaded with the core action followed by the most safety-relevant requirements. Every sentence contributes actionable information with no filler.

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 6-parameter create operation with no annotations and no output schema, this description is too sparse. It omits the expected return value, side effects, duplicate handling, email notification behavior, and any guidance on the password parameter beyond what the schema already states.

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 only 33%, and the description only adds one meaningful semantic fact beyond the schema: the administrator role requires explicit confirm. It does not explain username, email, display_name, or role semantics beyond what the schema already provides, so it fails to compensate 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: 'Create a WordPress user.' This clearly distinguishes it from user read tools like wp_get_user and wp_list_users, as well as from the many other create_* siblings.

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 provides operational prerequisites ('confirm:true required in safe mode') but gives no guidance on when to prefer this tool over alternatives or when not to use it. The safe-mode note implies usage context, but no exclusions or alternative routing are provided.

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