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 fully covered. The description adds genuinely new context by disclosing that authentication is local WordPress auth with no WooCommerce REST API keys needed, but says nothing about return shape 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 short sentences with the action front-loaded and no filler. The implementation note about mirroring the woocommerce-mcp-server method is marginal for tool selection but is not disruptive.

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 list operation with full annotations, a fully documented single parameter, and no output schema, the definition is nearly sufficient. The only gap is the absence of any hint about what a tax class record contains, which would help the agent chain calls.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains site_id thoroughly, including the warning not to pass a URL or post ID. The description adds no additional meaning about the parameter, so the high-coverage 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?

The description states a specific verb and resource ("Retrieves WooCommerce tax classes"), which cleanly separates it from sibling mutators such as wc_create_tax_class and wc_delete_tax_class. It does not explicitly contrast itself with wc_get_tax_rate/wc_get_tax_rates, so an agent must still infer the plural/collection scope.

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 offers no when-to-use guidance, no prerequisites, and no named alternatives. The only procedural hint (call list_sites first) lives in the schema, not the description, so an agent reading the prose alone gets no routing signal.

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