woocommerce_create_product_attribute

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

With no annotations provided, the description carries the full burden. It successfully communicates that these are 'global' attributes (a key WooCommerce behavioral distinction) and their relationship to variable products, but fails to disclose mutation side effects, idempotency, error scenarios, or return value structure.

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 compact with two efficient sentences. The '[UNIFIED]' prefix appears to be metadata noise but doesn't significantly detract. Information is front-loaded with the action verb. Every sentence earns its place.

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?

Given 6 undocumented parameters (0% schema coverage), no annotations, and no output schema, the description is insufficient. It lacks parameter documentation, return value description, and error handling guidance necessary for a creation tool with multiple configuration options.

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?

The schema has 0% description coverage for all 6 parameters (site, name, slug, type, order_by, has_archives). The description provides conceptual examples (Size, Color) but completely fails to document the actual parameters, their formats, or valid values for fields like 'type' and 'order_by'.

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 specific action (Create), resource (global product attribute), and intended use case (for variable products). It distinguishes from sibling tools by specifying 'attribute' rather than 'product' or 'variation', and clarifies these are 'global' attributes with concrete examples (Size, Color).

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 phrase 'for use in variable products' provides implied context about when to use this tool, but lacks explicit guidance on when NOT to use it (e.g., for local attributes) or alternatives like woocommerce_list_product_attributes for reading existing attributes.

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