WooCommerce Produkte auflisten

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'lists with filters' and gives no information about pagination, default sort order, result limits, or any side effects. This is a significant gap for a tool with 13 parameters, leaving the agent unaware of response structure or operational constraints.

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 with no fluff. It front-loads the core purpose and is easily scannable. However, it is arguably too brief to convey needed guidance, though that is a completeness issue, not a conciseness one.

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 complexity (13 optional parameters, no output schema, no annotations), the description is woefully incomplete. It fails to explain pagination behavior, result limits, sorting defaults, or how filters interact. A one-sentence description cannot adequately cover this functionality.

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 description coverage is 100%, meaning every parameter already has a description (e.g., 'Tag-ID', 'Seite', 'Nur Sale Produkte'). The description adds little beyond the generic 'with filters', so it meets the baseline for schema-driven tools but provides no additional semantic enrichment.

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 it lists WooCommerce products with filters, using the verb 'listet' and specifying the resource. While it doesn't explicitly name alternatives, the focus on products distinguishes it from sibling tools like woo_list_orders or woo_list_categories, making the purpose unambiguous.

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. The description provides no context about scenarios where listing products is appropriate, nor does it contrast with related list tools (e.g., woo_list_variations). This leaves the agent to infer usage solely from the name and schema.

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