wp_list_products

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

With no annotations provided, the description carries the full behavioral burden. "List" implies a read-only operation and "optional filters" suggests filtering, but the description does not disclose pagination behavior, default values, response shape, or whether any statuses or search terms have special semantics.

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 one front-loaded sentence with no wasted words. It states the primary action and resource immediately. It is concise, though somewhat under-specified, which prevents a perfect score.

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 tool with no annotations, no output schema, and sparse parameter documentation, this one-line description is not fully complete. It omits filter semantics, pagination behavior, and return expectations, leaving important context to inference.

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 only 25%, covering just the status parameter. The description adds only the generic phrase "optional filters" and does not explain page, search, per_page, or the meaning of status values beyond the schema. It fails to compensate for the low schema coverage.

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 names a specific verb and resource: "List WooCommerce products." This distinguishes it from single-product tools like wp_get_product and from wp_list_booking_products. However, "optional filters" is vague and does not identify which filters are available, so it falls just short of being fully specific.

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?

There is no guidance on when to use this tool versus alternatives such as wp_get_product for a single product or wp_list_booking_products for booking products. No exclusions, prerequisites, or scenarios are given, so the agent must infer usage entirely from the name and minimal description.

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