wordpress_get_users

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

The description claims role filtering, but the schema includes only perPage and page parameters, with no role field. This is a direct contradiction between description and schema, misleading about the tool's 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 very concise (5 words), but this conciseness comes at the cost of accuracy and completeness. It is not structured to highlight key details.

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?

Lacks essential details: no mention of pagination behavior, return format, or that the schema lacks the claimed role filtering. With no output schema, this leaves the agent underinformed.

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 adds no information about the two parameters (perPage, page). It fails to explain their meaning or usage, leaving the agent to infer from parameter names only.

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 'Get WordPress users' which clearly identifies the resource and action, but adds 'with role filtering' which is not supported by the input schema (no role parameter), making it somewhat misleading.

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 on when to use this tool versus alternatives like wordpress_get_roles or wordpress_search_posts. The description does not differentiate context or provide exclusion criteria.

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