WooCommerce MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool searches products, implying it's a read-only operation, but doesn't mention any behavioral traits such as pagination (though 'per_page' in the schema hints at it), rate limits, authentication requirements, or what the search returns (e.g., partial matches, case sensitivity). This leaves significant gaps for a tool with parameters.

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, efficient sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple search tool, making it easy to parse quickly.

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 tool's moderate complexity (2 parameters, no annotations, but an output schema exists), the description is minimally adequate. The output schema likely covers return values, reducing the need for description details there. However, with no annotations and low schema coverage, the description lacks context on behavior and parameter usage, making it incomplete for optimal agent understanding.

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%, so the description must compensate for undocumented parameters. It mentions 'by name or SKU,' which relates to the 'query' parameter, adding some semantic context. However, it doesn't explain the 'per_page' parameter or provide details on query syntax (e.g., wildcards, exact matches). With 2 parameters and low schema coverage, the description adds limited value beyond the schema.

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 tool's purpose: 'Search products by name or SKU.' It specifies the verb ('Search') and resource ('products'), and mentions the searchable fields (name or SKU). However, it doesn't distinguish this from sibling tools like 'list_products' or 'get_product', which might offer alternative ways to retrieve product data.

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 doesn't mention sibling tools like 'list_products' (which might list all products without filtering) or 'get_product' (which might retrieve a single product by ID), nor does it specify prerequisites or exclusions. Usage is implied but not explicitly defined.

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