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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by explaining the authentication model — local WordPress auth, no WooCommerce REST API keys required — but says nothing about the shape or volume of the returned method list.

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 tight sentences, front-loaded with the purpose, with the second carrying genuinely useful authentication context rather than filler. Nothing is redundant, though the second sentence is implementation trivia relative to the missing sibling disambiguation.

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 one-parameter read tool with full annotation and schema coverage, the basics are present, and the auth note fills a real gap. The remaining hole is scope: the description never clarifies whether results are global method definitions or zone-scoped, which is exactly the confusion its sibling names create.

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?

With a single parameter at 100% schema description coverage, the schema already explains site_id and even warns to call list_sites first rather than passing a URL or post ID. The description adds nothing beyond that, so the baseline of 3 applies.

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 available WooCommerce shipping methods.' That is clear enough to act on, but it does not distinguish this from the closely named sibling wc_get_shipping_zone_methods, leaving ambiguous whether 'available methods' means global method types or methods attached to a zone.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent facing both this tool and wc_get_shipping_zone_methods gets no signal about which one to pick, and must infer it from the name alone.

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