woocommerce_list_product_attributes

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

No annotations provided, so the description carries full disclosure burden. It mentions 'List all' implying comprehensive retrieval, but lacks information on safety (read-only vs write), rate limits, return format, or pagination behavior.

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 appropriately brief with two sentences. The core purpose is front-loaded, though the '[UNIFIED]' tag at the beginning is unnecessary metadata that doesn't serve the agent.

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 single-parameter list tool without output schema, the description adequately explains what product attributes are with concrete examples (Size, Color). However, it fails to document the required 'site' parameter, leaving a significant gap.

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 0% for the required 'site' parameter. The description provides no explanation of what 'site' refers to (domain, ID, etc.) or its format, failing to compensate for the undocumented schema.

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 clearly states the verb (List) and resource (global WooCommerce product attributes), and distinguishes from product-specific attributes by specifying 'global.' The '[UNIFIED]' prefix is extraneous metadata that slightly reduces clarity.

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?

No explicit guidance on when to use this tool versus alternatives like woocommerce_list_products or woocommerce_list_product_variations. While it mentions attributes are used for variations, it doesn't indicate prerequisites or selection criteria.

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