wp_update_user

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It doesn't state whether authentication is required, whether updates are partial or full, what happens to unmentioned fields, or any other operational characteristics. A mutation tool with zero annotation coverage needs more context.

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?

Extremely terse at four words, which is concise but under-specified for a six-parameter mutation tool. It's front-loaded with the core action, but the brevity leaves critical information missing.

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?

This is a mutation tool with six parameters, one required, no annotations, no output schema, and very low schema description coverage. The description fails to provide necessary context about permissions, partial update behavior, or parameter semantics, making it inadequate for an agent to use safely and correctly.

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 17%, with just the 'id' parameter described as 'User ID'. The remaining five parameters (role, email, username, last_name, first_name) have no descriptions in either the schema or the tool description, leaving their semantics and constraints undocumented. The description does not compensate for this 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?

States a specific verb (update) and resource (WordPress user). Sibling tools like wp_update_post and wp_update_page make the CRUD pattern predictable, though the description doesn't explicitly distinguish itself from other update tools, which is acceptable given the clear naming convention.

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?

No guidance on when to use this tool versus alternatives like wp_add_user or wp_delete_user. The description merely restates the operation without context about prerequisites, permissions, or when to prefer this over other user management tools.

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