WooCommerce: List product attributes

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

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the description only needs to add scope context, and it does: results are store-wide "global" attributes, not per-product ones. It says nothing about pagination, ordering, or whether attributes with zero terms are included, which are the traits an agent would actually need beyond the annotation.

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 and scope, and the second sentence earns its place by explaining what the resource is for. No filler or repetition of the title beyond the initial phrase.

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 tool with no output schema, the description covers what the tool returns at a conceptual level and what the resource means. It is incomplete on the one required input (site) and lacks any hint about result shape or volume, which matters when no output schema exists.

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 one required parameter (site) at 0% schema description coverage, so the description carries the full burden of explaining it — and it never mentions the parameter at all. The sentence about variations does not compensate for the completely undocumented site argument.

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 ("List all global WooCommerce product attributes") and the "global" qualifier separates it from product-scoped lookups. The meaning of the resource is clarified with the Size/Color example. It does not explicitly name create_product_attribute or delete_product_attribute as the non-listing siblings, but the verb itself makes the distinction clear.

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 note that attributes drive product variations, which hints you would call this before creating variations or filtering products. There is no explicit when-to-use statement, no prerequisites (e.g., need an attribute ID first), and no exclusions relative to the sibling create/delete attribute tools.

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