pressable_list_wp_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. It only restates the tool's purpose without disclosing behavioral traits such as pagination limits, error handling, or read-only semantics. The sentence adds nothing beyond what the tool name already implies.

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, concise sentence that immediately states the purpose. There is no filler, redundant detail, or unnecessary structure, making it appropriately front-loaded and efficient.

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?

Given the simple tool and lack of output schema, the description is still incomplete. It does not clarify the required 'id' parameter's role, explain the optional pagination parameters, or indicate what the response will contain. This leaves a new agent without essential operational details.

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?

The input schema has three parameters (id, page, per_page) with no descriptions (0% schema coverage). The description does not explain the meaning of 'id' directly, though it implies a site ID. Pagination parameters are completely unaddressed, so the description fails to compensate for the absence of schema descriptions.

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 'List WordPress users for a specific site' clearly states the action (list) and resource (WordPress users), with an explicit scope ('specific site'). This distinguishes it from sibling list tools like pressable_list_sites or pressable_list_plugins.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that the 'id' parameter is required, nor does it offer any exclusions or prerequisites. No context about site-level permissions or choosing this over other list tools is given.

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