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

The description does add genuine behavioral context beyond the annotations: it is a non-mutating preview, it returns a confirmation link, and only the merchant can complete it. However, the explicit claim "Calling this changes nothing" directly conflicts with readOnlyHint=false, which declares the tool is not read-only; that inconsistency undermines the reliability of the disclosure.

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?

Four short sentences, front-loaded with the verb and with no filler; the flow caveat is placed before the merchant-only constraint. The cents note is slightly redundant with the schema, keeping it from a 5.

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?

With no output schema, the description usefully characterizes the return (a preview and confirmation link), which is the most important thing to know. But parameter semantics are thin for a 9-param tool, and the read-only conflict leaves the agent unsure whether the call has side effects.

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 only 44%. The one parameter fact the description supplies ("Money is integer minor units (cents)") merely repeats the price field's own schema description, and sku, tags, title, vendor, and description are left undocumented in both places, so the description does not 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?

"Add a product" gives a specific verb + resource, and the create intent is separable from siblings like products_edit, products_delete, and products_set_status. It stops short of naming those alternatives, so an agent gets the core purpose but no explicit sibling routing.

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 description explains the mechanics of the call (preview + confirmation link) but never states when to use this versus products_edit, products_bulk_price_edit, or collections_add_products. There is no when-not-to-use guidance, so selection is left to inference from the name.

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