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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description's "read-only, runs straight away" mostly restates that, adding only the no-prompt nuance. It does not disclose the shape of the statistics returned or whether numbers are cached.

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?

One short sentence with the resource and metric scope front-loaded. The parenthetical site name and "Through Royally" prefix are mild noise but not costly.

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?

For a zero-required-parameter read-only stats tool this is close to sufficient: it says what data family is returned and which period values are selectable. The main remaining gap, the exact metrics and structure of the response, is modest for a summary-statistics tool with no output schema.

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 description coverage is 100% and both parameters carry enums with descriptions, so the description needs to add nothing and adds nothing. Baseline 3 applies.

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?

States a specific verb (Get) and resource (WooCommerce store statistics) and enumerates the metric families covered (revenue, orders, products). It is clearly a reporting tool rather than an order-listing tool, though it never names the sibling reporting alternatives.

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?

"Runs straight away" hints that no confirmation step is needed, and the site scoping is stated, but there is no explicit when-to-use guidance versus wc_get_orders or wc_get_products when an agent actually wants revenue data. Usage is only implied.

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