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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description adds genuinely new behavioral context by explaining the auth model (local WordPress authentication, no WooCommerce REST API keys required). It says nothing about pagination limits or result volume, which matters for a list endpoint.

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 purpose front-loaded and no filler. The second sentence's reference to mirroring the upstream server method is mildly internal-facing, but it earns its place by justifying the authentication claim that follows.

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 read-only paginated list tool with full schema coverage and a nested filters object, the description covers purpose, auth requirements and safety context. The absence of an output schema means the return shape of tax rate objects is left implicit, which is the main remaining gap but a modest one for a well-known resource.

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 page, perPage, site_id and the filters passthrough object are already documented in structured data. The description adds no parameter meaning beyond that, including nothing about what filters keys are accepted for tax rates. Baseline 3 is appropriate.

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 WooCommerce tax rates"), which is unambiguous on its own. It does not, however, distinguish itself from the singular sibling wc_get_tax_rate or from wc_get_tax_classes, so the agent must infer that this is the list endpoint.

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 guidance at all: nothing says when to prefer this over wc_get_tax_rate or wc_get_tax_classes, and no prerequisites or exclusions are stated. The only routing hint an agent gets comes from the input schema's site_id note ("Call list_sites first"), not from the description.

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