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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower. The description still adds real context beyond them: new products default to draft status, and WooCommerce must be active. It omits the permissions required and what happens on duplicate SKUs, hence not a 5.

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 action and scope, then defaults, then prerequisite. No filler and nothing repeated.

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?

An output schema exists so return values need not be explained, and annotations plus the draft-default notice cover the mutation's basic behavior. Still, with 7 undocumented parameters and only a name requirement in the schema, an agent lacks the detail needed to supply sku, price, stock, and site_url correctly.

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% across 7 parameters, so the description carries the burden and largely fails. It only alludes to the status default ('Defaults to a draft'), saying nothing about sku uniqueness, price format, stock type, site_url targeting, or description content. Most parameters are left unexplained.

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 ('Create a WooCommerce simple product') plus the hosting context ('on a connected WordPress site'). The 'simple product' qualifier usefully scopes it away from other WooCommerce product types. It does not explicitly name or distinguish itself from siblings like wordpress_woo_products, so it stops short of a 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?

Gives a prerequisite ('Requires WooCommerce to be active') and a default behavior, which implies the creation context. However, it offers no when-to-use vs alternative guidance (e.g., list via wordpress_woo_products, update via a future update tool) and no exclusions.

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