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 structurally. The description adds real value beyond that: a mandatory human-confirmation workflow before confirm=true, and authentication context (local WordPress auth, no REST keys needed), which an agent needs to execute correctly.

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 purpose, then the confirmation requirement, then auth context. Minimal waste; the 'mirrors woocommerce-mcp-server method delete_attribute_term' clause is slightly meta but earns its place by flagging the auth model.

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 destructive 5-parameter mutation with no output schema, the definition covers purpose, confirmation protocol, and auth model — the essentials an agent needs. It does not describe the post-deletion return value or edge behavior (e.g., what happens if the term is assigned to products), which is a minor gap given annotations carry the safety signals.

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 site_id, attributeId, termId, confirm, and force are all documented in the schema itself. The description only restates the confirm gating already implied by the schema's confirm field and adds no new parameter meaning; baseline 3 applies.

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 with scope: 'Deletes a term from a WooCommerce product attribute', which is inherently distinguishable from wc_delete_product_attribute or wc_delete_attribute_term's create/get/update siblings. It does not explicitly name a contrasting sibling, so it stops short of a full 5.

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?

Provides a clear procedural precondition (get user confirmation, then pass confirm=true), which implies when the tool should fire. However it gives no guidance on alternatives (e.g., updating instead of deleting a term) or when deletion should be avoided, so usage context is only implied beyond the confirm gate.

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