WooCommerce Top-Seller

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'fetches' and does not mention whether the operation is read-only, how the period parameter affects results, whether there is a default limit, or what the return structure looks like. This is insufficient for a tool with no annotation support.

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 one short sentence with no wasted words. It is front-loaded with a clear verb and resource, making it easy to parse at a glance. Given the simplicity, this level of conciseness is appropriate, though it sacrifices completeness.

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?

The tool is simple but the description is very thin. There is no output schema, so the description should explain what the response includes (e.g., product IDs, quantities, dates). Nor does it mention the 'period' parameter, which is the only input, or how this report differs from the sales report. The minimal context makes it hard for an agent to understand the exact scope and return value.

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% coverage with a single parameter 'period' and a description 'Zeitraum'. The tool description adds no extra meaning beyond the schema, so the baseline of 3 applies. It does not clarify how period values (week, month, last_month, year) influence the aggregation or if any other filtering exists.

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 'Ruft die meistverkauften Produkte ab' clearly states the action (fetch) and the resource (best-selling products). It distinguishes itself from sibling tools like woo_get_sales_report or woo_list_products by focusing specifically on top sellers.

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_sales_report or woo_list_products. There are no exclusions or context hints to help an agent decide between similar WooCommerce reporting tools.

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