List users

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states 'List users on the site with their roles.' It does not disclose that this is a read-only operation, mention pagination behavior, or describe the output format beyond roles. There is no added context about permissions, rate limits, or filtering capabilities.

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 a single, clear sentence that front-loads the core action and resource. No unnecessary words or redundant information. It is an appropriate length for a simple listing tool.

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?

The tool has 4 parameters and no output schema or annotations. The description is too minimal to be complete. It does not mention pagination, filtering by roles/search, the default site behavior, or what the returned user data includes (e.g., usernames, emails, etc.). For a tool with no annotations, the description should provide more operational context.

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 50% (site and roles have descriptions; search and per_page do not). The description does not compensate for the missing parameter details. It mentions 'with their roles' but does not explain how the roles parameter works, nor does it explain the search or per_page parameters. The description adds minimal value beyond 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 lists users on the site and includes their roles. The verb 'List' and resource 'users' are specific and unambiguous, distinguishing it from sibling tools like wp_list_post_types or wp_list_taxonomies.

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 states the tool lists users, which implies it is the appropriate choice for retrieving user data. However, it does not explicitly mention when not to use it, such as for listing roles (use wp_list_terms) or other resources. The usage context is implied by the resource name but not explicitly contrasted with alternatives.

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