wp_list_users

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

There are no annotations, so the description carries the full behavioral burden. It does disclose that WP_USERNAME/WP_APP_PASSWORD is required for full details, which is useful. However, it does not clarify what happens without credentials, whether the operation is explicitly read-only, or any pagination or rate-limit behavior.

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 extremely concise: two short sentences with no filler. The core purpose is front-loaded, and the authentication note is a valuable second sentence that earns its place.

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 simple list operation with one optional parameter, this description is minimally adequate. It gives the purpose and mentions an auth requirement, but it is vague about what 'full details' means, how credentials are supplied, and what the response looks like. Given the absence of annotations and an output schema, more context would be helpful.

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?

The input schema has zero description coverage for the only parameter, per_page, and the tool description does not mention it either. The parameter name and min/max constraints are somewhat self-explanatory, but the description adds no meaning about pagination or how the parameter affects results.

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 the core action clearly: 'List WordPress users.' This is a specific verb and resource that distinguishes it from sibling tools like wp_list_posts or wp_list_pages. However, it does not add any scope or filtering details to further differentiate it from other list tools.

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 is given about when to use this tool versus alternatives such as wp_list_posts, wp_list_categories, or wp_request. The only conditional information is the authentication requirement, which is a prerequisite rather than a usage guideline.

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