WooCommerce Bestellungen auflisten

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

With no annotations provided, the description must disclose behavioral traits, but it only states the basic action. It does not mention pagination behavior, default return size, whether results are read-only, authentication needs, or any side effects. This lack of detail leaves important operational unknowns.

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 filler, but it largely restates the tool title 'WooCommerce Bestellungen auflisten', adding no new information. While succinct, it fails to earn its place by providing redundant rather than complementary content.

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 six parameters, no annotations, and no output schema, a one-line description is insufficient. It does not explain what the response contains, how filtering parameters interact, or the safety profile of the operation, leaving substantial gaps for the agent.

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 input schema has 100% description coverage for all six parameters (page, after, before, status, perPage, customer), so the baseline is 3. The tool description itself adds no parameter context, but the schema's brief descriptions like 'Seite' and 'Status' sufficiently convey basic parameter semantics.

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 'Listet WooCommerce Bestellungen auf' clearly states the verb (list) and resource (WooCommerce orders), making the primary function obvious. However, it does not specify scope (e.g., all orders vs. filtered) or explicitly differentiate from sibling tools like woo_get_order, so it stops short of a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives such as woo_get_order or woo_list_customers. The description simply states what it does, leaving the agent to infer usage context from the tool name and sibling list.

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