wp_woocommerce_create_tax_rate

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. 'Create a new' signals a write operation, but it does not mention persistence, permission requirements, duplicate handling, side effects on checkout, or whether the rate is immediately active.

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 a single efficient sentence with no wasted words and the core action is front-loaded. It is concise, though it sacrifices useful context for brevity.

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?

With no output schema and no annotations, the description is too thin for a 7-parameter mutation tool. It does not state what the tool returns, how to confirm success, whether the rate applies immediately, or what prerequisites exist beyond the schema parameters.

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?

The input schema already documents all 7 parameters with 100% coverage, so the baseline is 3. The description adds minimal parameter-level insight beyond pointing at country/state scope, which the schema already covers.

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 uses a specific verb and resource: 'Create a new WooCommerce tax rate.' It also adds scope ('for a specific country/state'), which makes the tool's purpose concrete and distinguishable from sibling tools like wp_woocommerce_list_tax_rates or wp_woocommerce_create_coupon.

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 states what the tool does but gives no guidance on when to choose it over alternatives, nor any exclusions. There is no mention of checking existing tax rates first, verifying WooCommerce status, or when create_coupon or update_settings would be more appropriate.

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