WooCommerce Verkaufsreport

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

With no annotations, the description carries full responsibility for behavioral disclosure. It merely states 'retrieves sales statistics' without indicating whether the operation is read-only, what the response structure looks like, or how date parameters influence the query. This is minimal and leaves the agent without important context.

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, short sentence that is front-loaded and free of unnecessary text. It is concise but borders on being too terse, doing the minimum to convey the core purpose. Still, it earns points for efficiency.

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 there is no output schema and no annotations, the description should clarify what 'sales statistics' includes (e.g., revenue, order counts) and how the parameters interact (e.g., whether period overrides date range). It does neither, leaving the agent uncertain about the tool's behavior 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 schema provides full descriptions for all three parameters ('Zeitraum', 'End-Datum', 'Start-Datum'), giving 100% coverage. The tool description does not add any additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 Verkaufsstatistiken ab' clearly states the action (retrieve) and resource (sales statistics), giving a basic understanding of the tool's function. However, it does not differentiate this tool from sibling tools like woo_get_top_sellers, which also deals with sales-related 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, such as whether to use it for overall sales trends vs. top sellers, or when to use period vs. date range parameters. There are no context cues, exclusions, or alternative tool references.

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