wordpress_list_users

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

No annotations provided, so description carries full burden. It discloses pagination behavior and enumerates return fields (name, username, email, roles) which compensates partially for missing output schema. However, missing safety classification (read-only implied but not stated), rate limits, or error conditions.

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?

Two sentences with clear structure: action followed by return specification. Front-loaded with the verb. Minor deduction for the non-semantic '[UNIFIED]' metadata prefix which wastes tokens without adding agent value.

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 4-parameter list operation with no output schema, the description adequately covers return value structure but leaves critical input semantics undocumented. Acceptable baseline for simple tools, but parameter documentation gap is significant given zero schema coverage.

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 has 0% description coverage, and the description fails to compensate. No explanation of 'site' format (URL vs ID), 'roles' filter syntax, or pagination limits (max per_page). The mention of 'roles' refers to return values, not the filter parameter.

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 specific verb 'List' and resource 'WordPress users' clearly. The '[UNIFIED]' prefix is noise but doesn't obscure meaning. Implicitly distinguishes from sibling wordpress_get_current_user by emphasizing 'paginated list' (plural) vs singular retrieval, though explicit differentiation would strengthen it.

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?

Mentions 'paginated' which implies usage pattern (handling pages), but lacks explicit when-to-use guidance versus alternatives like wordpress_get_current_user. No mention of required permissions or prerequisites for accessing user data.

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