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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context the annotations cannot: it runs on local WordPress authentication and needs no WooCommerce REST API keys. It does not explain what a duplicate create does or what the response contains.

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 action; the second sentence earns its place by explaining the authentication model. No filler.

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?

taxRateData is a free-form nested object with additionalProperties=true and no documented fields, and the description does nothing to say which tax-rate fields are accepted or required. For a mutation tool with a nested payload, that leaves a real gap, though annotations and the site_id note cover the rest.

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 parameters are already documented, and the description adds no field-level meaning for taxRateData. Baseline 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: "Creates a WooCommerce tax rate." That cleanly separates it from the get/update/delete tax-rate siblings, though it never names them explicitly.

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 by the verb "creates"; there is no explicit statement of when to use this versus wc_update_tax_rate or wc_create_tax_class. The site_id schema note (call list_sites first) supplies the one real prerequisite, but that lives in the schema, not the description.

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