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

Annotations already declare destructive=true, idempotent=false, and openWorldHint=true, so the safety profile is covered. The description adds that it mirrors the woocommerce-mcp-server method and needs no WooCommerce REST API keys, but does not explain what the destructive behavior entails or whether duplicates are possible.

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 front-loaded sentences with no filler: the first states the action, the second supplies authentication context. The mirroring detail is marginally meta but still relevant to setup expectations.

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 three-parameter create tool with a nested free-form methodData object and no output schema, the definition is adequate but thin. It does not hint at what the returned created method contains or what fields methodData accepts.

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%, including the site_id instruction to call list_sites first, so the schema carries parameter semantics. The description adds no meaning beyond the schema about zoneId or the nested methodData fields.

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: "Creates a shipping method in a WooCommerce shipping zone." This clearly separates it from sibling tools like wc_create_shipping_zone or wc_update_shipping_zone_method, though it does not explicitly name those alternatives.

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?

Says what it does but gives no guidance on when to choose it over wc_update_shipping_zone_method or when to avoid creating a duplicate method. The authentication note (local WordPress auth, no REST keys) is useful context but not usage guidance.

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