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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: authentication runs through local WordPress rather than WooCommerce REST API keys. It does not disclose return shape, whether all zones come back at once, or pagination behavior, which matters for a list tool.

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?

Two short sentences, front-loaded with the resource being retrieved and followed by the authentication note. No filler, though the "mirrors woocommerce-mcp-server method" phrasing is implementation-oriented rather than task-oriented.

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?

The tool is a simple read with full annotation coverage, a fully described schema, and no output schema, so the description is nearly sufficient. The gap is the absence of any statement about result scope or ordering for a list operation, and the opaque filters parameter is left entirely to the 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%, so both site_id and the filters object are documented in the schema itself, including the instruction to call list_sites first. The description adds no meaning about the filters object (its properties are empty and open-ended) or about what filter keys WooCommerce accepts. Baseline 3 is appropriate where the schema does the heavy lifting.

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 gives a specific verb and resource ("Retrieves WooCommerce shipping zones"), and the plural form implicitly contrasts with the singular wc_get_shipping_zone sibling. It stops short of explicitly stating the list-vs-single distinction, so an agent must infer it from naming alone.

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?

Usage is only implied: this is the plural list operation, so it is the right call when the agent wants all zones rather than one. There is no explicit when-to-use or when-not guidance, and no mention of alternatives such as wc_get_shipping_zone or the zone-locations/methods tools.

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