List WooCommerce Shipping Zones

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

With readOnlyHint=true already provided by annotations, the description adds value by specifying that the output includes both shipping zones and their methods, which is not evident from the tool name alone. It also suggests a practical use case (verifying shipping is disabled). No contradiction with annotations.

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 extremely concise: two short sentences that immediately state the function and provide the primary use case. Every word earns its place, with no filler or repetition.

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 simple read-only list tool with a single optional parameter and no output schema, the description covers the key aspects: what is returned (zones and methods) and when to use it. It could theoretically detail output formatting, but the parameter description covers that, and the scope is minimal.

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% for the single parameter (response_format), which is fully documented with an enum and default. The description does not add any information about parameters, but it doesn't need to because the schema is self-explanatory. Baseline 3 is appropriate.

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 clearly states the tool's purpose: 'List shipping zones and their methods.' This uses a specific verb ('list') and a specific resource ('shipping zones'), and goes beyond the title by mentioning methods, which distinguishes it from other list tools in the sibling set (e.g., wc_list_products, wc_list_orders).

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 clear context: 'Use to verify shipping is disabled or check what zones exist.' This tells the user when to invoke the tool. It does not explicitly name alternatives or state when not to use, but given the simplicity and lack of overlapping sibling tools, this is sufficient.

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