Create a user

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

Annotations already mark readOnlyHint=false and destructiveHint=false. The description adds behavioral context beyond that by stating the requirement for an Administrator account and the full-control implication of the 'administrator' role, which is not present in the annotations. No contradiction exists.

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?

Two crisp sentences: the first states the core purpose, the second delivers the role warning. No redundant content; every word earns its place and the critical caution is front-loaded.

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 11 parameters, 3 required, and no output schema, the description covers the essential purpose and the most impactful behavioral warning (role implications). It omits return-value expectations and error handling, but given full schema coverage and clear purpose, it is reasonably complete for a creation operation.

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 100%, so the baseline is 3. The description adds value beyond the schema by advising deliberate role selection and warning that 'administrator' grants full control, a nuance not captured in the schema's role description. This extra semantic guidance raises the score above baseline.

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 ('Create'), a clear resource ('a WordPress user'), and adds an important scoping detail (requires Administrator account). It distinguishes from sibling tools like update_user and delete_user by specifying the creation action, making the purpose unmistakable.

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 explicitly mentions a prerequisite (Administrator account) and warns about the consequences of the 'administrator' role, which guides when and how to use it. It does not explicitly contrast with alternatives like update_user, but the purpose is self-evident and the cautions provide practical usage direction.

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