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

Annotations already set readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true. The description adds genuinely useful context beyond that: it runs over local WordPress authentication and needs no WooCommerce REST API keys. It does not disclose duplicate-name behavior, error modes, or what is returned after creation.

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 verb and resource. The second sentence is a useful operational note rather than filler, though the implementation-detail framing ('mirrors woocommerce-mcp-server method') is of marginal value to an 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 three-parameter creation tool with no output schema, the description omits the shape of termData and gives no hint about the response (e.g., the created term ID), which an agent would need to chain into subsequent calls. The authentication note partially compensates.

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 coverage is 100%, so site_id and attributeId are already documented in the schema. However, termData is declared as an empty object with additionalProperties=true, so the description should have named the accepted term fields (name, slug, description, menu_order) but instead says only 'Attribute term fields to create.' That is the one place extra meaning was needed and none was supplied.

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: creating a term for a WooCommerce product attribute. That distinguishes it from wc_create_product_attribute and the update/get/delete term siblings without the agent opening schemas, though it never explicitly contrasts with them.

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: the tool creates a term, so it follows an existing attribute and precedes term listing/updating. There is no statement of prerequisites (e.g., the attribute must already exist) or of when to prefer this over wc_create_product_attribute.

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