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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context about local WordPress authentication and no REST API key requirement, but says nothing about return format, ordering, or pagination.

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 sentences, front-loaded with the core action and scope. The second sentence mixes a useful authentication note with an implementation detail about mirroring another server's method name, which is marginal for an agent but not harmful.

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, two-parameter getter with full schema coverage and rich annotations, the description covers the essentials plus the authentication model. It lacks return-value detail, but no output schema exists and this is a minor gap for a straightforward list retrieval.

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 zoneId and site_id are already fully documented, including the instruction to call list_sites first. The description adds no parameter-level meaning beyond the schema, which makes the baseline 3 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?

States a specific verb and resource ('Retrieves shipping methods') and scopes it to 'one WooCommerce shipping zone,' which distinguishes it from the sibling wc_get_shipping_methods and wc_get_shipping_zone without naming them. Clear enough that an agent can identify the operation.

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 usage through its scope but gives no explicit when-to-use guidance, no prerequisites beyond the schema, and no mention of when to prefer an alternative such as wc_get_shipping_methods or wc_get_shipping_zone.

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