wordpress_get_users

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read operation but fails to mention authentication, pagination behavior, response format, or the fact that role filtering is not actually available. The claim about role filtering contradicts the schema, making behavior misleading.

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 short and front-loaded, but the 'with role filtering' claim is not only unearned but false, so it does not fully earn its place. It is concise but not appropriately effective.

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 no output schema and no annotations. The description is a single sentence that omits essential details like pagination, return value, and actual filtering support. It also introduces a misleading capability, making it inadequate for an agent to correctly invoke the tool.

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 0%. The description should compensate but instead mentions a non-existent role filtering capability and says nothing about the actual parameters (page and perPage). It provides no meaning beyond the raw schema types.

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 action (Get WordPress users) and resource (WordPress users), but it adds 'with role filtering' which is not supported by the input schema (only page and perPage are allowed). This inaccuracy diminishes clarity and distinguishes it from siblings only vaguely.

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 provided about when to use this tool versus alternatives like wordpress_get_roles, wordpress_assign_role, or even wordpress_get_posts. There is no mention of typical use cases, prerequisites, or exclusions.

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