woocommerce_get_customer_report

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

No annotations provided, so description carries full disclosure burden. It reveals the fallback mechanism and return data type (count and spending), but omits safety characteristics, pagination behavior, rate limits, or output format structure. 'Get' implies read-only but this is not explicitly confirmed.

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?

Three sentences with zero redundancy. Front-loaded with action and resource. '[UNIFIED]' tag is slightly opaque without additional context but does not significantly bloat the text. Every sentence earns its place.

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?

Without output schema or annotations, the description covers core functionality and fallback behavior adequately. However, with 4 parameters at 0% schema coverage, the lack of parameter semantics and output structure details leaves gaps for a reporting tool with date filtering 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?

Schema coverage is 0% (no descriptions), yet the description adds no parameter guidance. It does not clarify the 'site' format (URL vs ID), 'period' values (week/month/year), or date string formats for date_min/date_max. Relies entirely on parameter names being self-evident.

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?

Clear verb 'Get' with specific resource 'customer statistics report'. The phrase 'Returns customer count and spending data' distinguishes this from sibling tools like woocommerce_list_customers (individual records) and woocommerce_get_sales_report (sales focus). The '[UNIFIED]' prefix hints at wrapper behavior.

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?

Provides specific behavioral guidance with 'Falls back to customer list if reports endpoint unavailable,' indicating error-handling behavior. However, lacks explicit guidance on when to choose this over woocommerce_list_customers (aggregated stats vs. individual records) or date range selection criteria.

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