wordpress_wc_get_sales_report

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

No annotations are provided, so the description must disclose behavior. It implies a read operation but does not explain the return format, data scope, pagination, or any potential side effects. This leaves the agent without critical behavioral 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, clear sentence: 'Get WooCommerce sales report/analytics'. It is front-loaded and contains no redundant words, perfectly concise for a tool with no parameters.

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?

There is no output schema or annotation, so the description should at least indicate what the sales report includes or what to expect as a response. It does not, leaving the agent with an incomplete understanding of the tool's output and capabilities.

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 tool has zero parameters, so the schema imposes no requirements. With no parameters to document, the description does not need to add parameter semantics, and a baseline score of 4 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 'Get WooCommerce sales report/analytics' uses a specific verb ('get') and a clear resource ('sales report/analytics'), which distinguishes it from sibling tools like wordpress_wc_get_orders. However, it is slightly vague about what the report contains, though the name resolves some ambiguity.

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 such as wordpress_wc_get_orders or wordpress_wc_get_top_sellers. The description only states the action, with no mention of use cases, exclusions, or complementary tools.

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