WooCommerce Kunden auflisten

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'Listet WooCommerce Kunden auf' (lists WooCommerce customers), offering no details on pagination, default role filtering, search behavior, or potential side effects. This is inadequate for a tool that appears to be a basic read operation.

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, straightforward sentence with no redundancy or unnecessary words. It is appropriately sized and front-loaded, delivering the key purpose immediately.

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 and no output schema, the description is incomplete. It does not explain return format, pagination defaults, or comparison with similar list tools, leaving gaps for an agent to make incorrect assumptions about behavior and output.

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 descriptions provide 100% coverage for all four parameters, but they are terse ('Seite', 'Rolle', etc.). The tool description adds no additional parameter meaning, so the baseline score of 3 applies, as the schema already does the heavy lifting.

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 Kunden auf' uses a specific verb ('listet') and a clear resource ('WooCommerce Kunden'), distinguishing it from sibling tools like woo_list_orders or wp_list_users. It unambiguously states the tool's core function.

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 wp_list_users or admin_list_users. There are no mentions of prerequisites, exclusions, or specific scenarios, leaving the agent without direction for tool selection.

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