woocommerce_list_products

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

With no annotations provided, the description carries the full burden. It discloses that results are paginated and lists the key data fields returned (pricing, stock status, categories), but omits information about rate limits, authentication requirements, or maximum page sizes.

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 efficiently structured with three sentences that each add value. The '[UNIFIED]' prefix is slightly noisy but doesn't significantly detract from the otherwise tight presentation.

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 lack of output schema and zero parameter descriptions, the description provides minimal viable context by mentioning pagination and return fields. However, it falls short of fully compensating for the missing structured metadata, leaving significant gaps in parameter documentation.

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 has 0% description coverage, so the description must compensate. While it mentions filtering by category, stock status, and search, it fails to document 6 of 9 parameters, including the required 'site' parameter, pagination controls (per_page, page), and the distinction between 'search' and 'search_terms'.

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 uses a specific verb ('List') with a clear resource ('WooCommerce products'), distinguishing it from sibling tools like woocommerce_get_product, woocommerce_create_product, and woocommerce_update_product. The scope is immediately obvious.

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 woocommerce_get_product (for retrieving a single product by ID) or woocommerce_search_products. It also lacks guidance on pagination handling for large result sets.

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