wp_list_users

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

Despite no annotations, description discloses read-only behavior, required permissions, and error-vs-crash outcome. It doesn't discuss pagination or rate limits, but with no annotation burden the description carries the main behavioral load well.

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?

Purpose and key constraints are front-loaded and compact, though the parenthetical '(that comes back as an error, not a crash)' is slightly redundant.

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?

Description includes output fields, permissions, and integration with sibling user tools, enough for a simple list. It lacks explicit install parameter description and pagination/limits, but remains largely self-contained.

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?

Search is fully explained as an optional substring matched against login/name/email, but the required install parameter is not explicitly defined beyond implying site context, leaving a gap with 0% schema coverage.

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?

Clearly states it lists a site's WordPress users with specific fields, and orients the caller to use returned IDs with wp_get_user/wp_update_user/wp_delete_user, distinguishing it from related user 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?

Explicitly notes read-only nature, describes search parameter behavior, and states admin app password requirement and failure mode, giving concrete conditions for use.

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