wp_comments_list

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

With no annotations, the description must carry the behavioral transparency burden. It adds useful semantic context by clarifying that 'Hold status = pending moderation', and 'List' implies a read-only operation. However, it does not disclose pagination behavior, default status, or other operational details beyond the filter list.

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 two sentences, front-loaded with the action and resource, and every clause provides useful information. There is no filler or redundancy.

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?

This is a 10-parameter tool with no annotations, no output schema, and zero schema-level descriptions. The description covers the core filtering idea but omits defaults, pagination, the distinction between order and orderby, and any permission or response details, leaving significant gaps for such a parameter-rich 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?

The schema provides no parameter descriptions (0% coverage), so the description needs to compensate. It names the major filter parameters and clarifies the status values, which adds some meaning. Yet it leaves several parameters (page, per_page, orderby, order) underspecified and collapses order/orderby into the vague term 'ordering'.

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 opens with a specific verb and resource: 'List comments', immediately distinguishing it from sibling comment tools like wp_comments_get, wp_comments_create, wp_comments_update, and wp_comments_delete. It also enumerates the filtering dimensions, making the scope clear.

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 clear context by stating this is a list operation with various filters, which implies when it should be used (when a collection of comments is needed). It does not explicitly name alternatives or exclusions, but the listing purpose is unambiguous and naturally differentiates it from single-comment operations.

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