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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly carried by structured data. The description adds the useful create-prerequisite constraint and that `quantity` sets inventory, but never warns that updating may overwrite unspecified fields or what happens to `quantity` when omitted.

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 create-versus-update condition, with every clause carrying information. No redundancy or 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 9-parameter destructive mutation this leaves meaningful gaps: which fields are create-only versus updatable, whether update is partial or a full replace (relevant given destructiveHint=true), and whether omitted fields are cleared. The output schema exists, so return values need not be described.

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 only 33% (id, quantity, business_id documented), and the description compensates for the most important gap by stating name and business_id are required on create, which the schema's empty `required` list does not convey. However it leaves sku, price, category, attributes, and description completely unexplained in both places.

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 product row / update one) and makes the mode switch explicit via the presence of `id`. It is clear enough to distinguish from the agent/lead/knowledge upserts in the sibling set, though it never names an alternative path.

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 concrete rule for the two modes: omit `id` to create, pass `id` to update, and states the create-time prerequisites (name and business_id). It stops short of saying when not to use this tool or what happens for bulk/product variants.

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