Update WordPress User

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

Annotations already indicate destructive and idempotent behavior. The description adds specific context by noting that roles replace existing roles and referencing demotion, which clarifies the destructive nature. No contradiction with annotations.

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 well-structured with a clear purpose, an Args list, and a Returns line. It is concise and front-loaded, though the Args list duplicates schema content; still every section serves a purpose.

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 tool with 10 parameters and no output schema, the description conveys the key use, the destructive role replacement behavior, and the return value. It is reasonably complete given the annotations and schema, though it omits explicit alternatives and edge cases.

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 schema already documents all parameters fully. The description's Args section largely repeats schema info, though it adds examples for roles and emphasizes required id. This is marginal added value over the schema.

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 updates an existing user's name, email, roles, or profile fields, with a specific verb and resource. It also distinguishes from siblings like wp_delete_user or wp_get_user by listing the updatable fields and giving a common use case (demoting an admin).

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 a common use case (demoting an admin) but does not explicitly mention when to avoid this tool or alternatives such as wp_bulk_update_users for batch updates. Usage guidance is implied rather than stated with exclusions.

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