wp_woocommerce_shipping_zones

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

With no annotations, the description carries the behavioral burden. It indicates a read/list operation and reveals that each zone includes configured shipping methods, but it does not mention pagination, ordering, empty-zone handling, or prerequisites such as WooCommerce being active.

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 front-loaded sentence with no filler. Every word adds relevant information about the operation and its output scope.

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 parameterless list operation, the description is sufficient to invoke the tool safely and to know the broad shape of the result. It is slightly incomplete because there is no output schema and the description only names the included methods without detailing zone fields or list behavior.

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 takes zero parameters, so there are no parameter semantics to document; the empty schema is fully consistent with the description. The baseline for a zero-parameter tool is a 4, as there is no ambiguity to resolve.

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 ('List') and a concrete resource ('WooCommerce shipping zones'), and adds that results include configured shipping methods. This clearly distinguishes it from sibling WooCommerce tools such as order, coupon, tax-rate, and settings tools.

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 gives a clear context: use it when you need to enumerate shipping zones and their methods. It does not explicitly name alternatives or exclusions, but no sibling tool covers shipping zones, so the selection context is unambiguous.

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