WooCommerce: Delete product attribute

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds real value beyond them: deletion is permanent, associated terms go with it, per-product custom attributes survive, and no trash/recovery state exists.

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?

Three short sentences, front-loaded with the destructive action, and each one carries distinct information (permanence, term cascade, product-level preservation, no trash). The '[UNIFIED]' prefix is the only filler.

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 two-parameter destructive mutation with no output schema, the description covers the consequential behavior an agent needs before calling: irreversibility, cascade to terms, and no trash recovery. It stops short of noting permission requirements or error behavior on an invalid attribute_id, which keeps it from a 5.

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 both parameters, and the description supplies no meaning for 'site' or 'attribute_id' — not even that attribute_id must reference an existing global attribute. The mention of attributes is topical, not parameter-level, so it fails to compensate for the coverage gap.

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 names a specific verb and resource ('Permanently delete a global WooCommerce product attribute') and clarifies scope by noting terms are included and per-product custom attributes are unaffected. That scoping distinction separates it from product/variation/category delete siblings, though it never names an alternative tool explicitly.

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 implied rather than stated: 'Attributes cannot be trashed' signals there is no soft-delete path, so this is the only removal route. There is no explicit when-to-use versus when-not-to-use guidance or named alternative (e.g., update vs. delete) for an agent weighing options.

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