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 carries the full burden of behavioral disclosure. It states 'Get' implies a read operation, but does not specify whether it requires authentication, returns real-time or historical data, includes pagination, or has rate limits. This is inadequate for a tool with zero annotation coverage.

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, efficient sentence ('Get WooCommerce sales report/analytics') with no wasted words. It is front-loaded and appropriately sized for a tool with no parameters, making it highly concise and well-structured.

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 the tool has no parameters (schema coverage 100%) and no output schema, the description is minimally adequate but lacks depth. It does not explain what the report includes (e.g., metrics, timeframes) or behavioral aspects like data format or access requirements, leaving gaps in context for effective use.

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 0 parameters with 100% coverage, so no parameter information is needed. The description does not add parameter details, which is acceptable given the schema's completeness. A baseline score of 4 is applied as it compensates appropriately for the lack of parameters.

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' clearly states the action ('Get') and resource ('WooCommerce sales report/analytics'), making the purpose evident. However, it does not differentiate from sibling tools like 'wordpress_get_media_analytics' or 'wordpress_get_performance_metrics', which also retrieve analytics, so it lacks explicit sibling distinction.

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 other analytics tools in the sibling list (e.g., 'wordpress_get_media_analytics'). There is no mention of context, prerequisites, or exclusions, leaving usage unclear beyond the basic purpose.

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