wp_woocommerce_status

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns store details and lists the categories, but it does not state failure behavior when WooCommerce is absent, whether the operation is read-only, or any permission/context requirements. The read-only nature is only implied by 'Check'.

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?

A single, front-loaded sentence conveys the operation and the main output categories with no filler or redundant detail.

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-parameter status check, the description gives the core output categories, but without an output schema it omits the actual result shape for both success and failure. 'Enabled features' also remains unspecified, leaving some ambiguity about interpretation when WooCommerce is not installed or active.

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?

This tool has no parameters, so the schema already fully covers this dimension. The description does not need to add parameter semantics, earning the baseline score of 4.

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 uses a specific verb ('Check') and resource ('WooCommerce installed and active'), and then clarifies what data is returned. This distinguishes it from sibling tools like wp_woocommerce_stats and wp_woocommerce_get_settings by its status-check intent.

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 implies it should be used when an agent needs to confirm WooCommerce is installed/active and get basic store context. However, it does not explicitly compare against overlapping siblings such as wp_woocommerce_stats, nor does it state when not to use it.

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