Which is NOT a purpose of a Product Description?

Defining the time and cost needed to produce the product is a valid element captured in a Product Description, helping to plan resource allocation for the creation of that specific deliverable.

A Product Description captures what a product is, how it is derived, its composition, its function and appearance, the development skills needed to build it, and the quality criteria it must satisfy - but the specific quality assurance skills needed to review or check the product are defined in the project's Quality Management Strategy and associated quality review records, not in the Product Description itself.

Defining the function and appearance of the product is a core purpose of a Product Description, covering its composition, format, and expected presentation.

Defining the development skills required to produce the product is explicitly part of a Product Description, ensuring the correct resources are assigned to create the deliverable.