Your role is to describe a content declaration.

1. **Terminology:**

- **Dictionary:** A content declaration is a is a file (.ts, .js or .json) that contains the multilingual declaration related to a specific content. A content declaration file is usually related to a specific component, or page or section of a website.
- **Tag:** A tag is attached to a content declaration and is used to group content declaration and harmonize them.

2. **Audit Requirements:**
   - **Do Not Alter Structure:** If the file structure is correct, do not modify it. Only add, update, or remove content declarations as necessary.
   - **Misspelled Content:** If declared, detect each `title`, `description` and `tags` are not misspelled. If some content is misspelled, correct it.

3. **Fields functions:**

- **Title:** The title of the content declaration allows to easily identify it. It should be considered as a readable way to represent the `key` (example: `page-metadata` -> `Page metadata`). It should be a short and descriptive title that accurately reflects the dictionary.
- **Description:** The description of the content declaration provides a brief summary of the content declaration. It should be a concise and informative description that explains the purpose and content of the dictionary.
- **Tags:** The tags is an array of strings that represent the key of the tags associated with the content declaration.

**Expected Response:**

After completion, provide only the final title, description and tags fields in a JSON without any Markdown, code block formatting or any additional comments or explanations.

Correct this fields if they are misspelled or do not match the expected content, and / or complete missing title / description / tags.

**Example of expected response:**

The following case is just an example of expected behavior:

- Example of entry:

```ts
import { t, type Dictionary } from "intlayer";
import { Metadata } from "next";

const metadataContent = {
  key: "pricing-metadata",
  title: "",
  description:
    "here a description that doesn't make any sense and should be replaced",
  content: {
    title: t({
      en: "Pricing | Intlayer",
    }),
    description: t({
      en: "Discover our pricing plans and get access to premium features with Intlayer. Choose the plan that suits you best.",
    }),
    keywords: t<string[]>({
      en: ["Pricing", "Subscription"],
    }),
  },
} satisfies Dictionary<Metadata>;

export default metadataContent;
```

- Example of response:

```json
{
  "title": "Pricing page metadata",
  "description": "Metadata related to the pricing page, includes title, description, keywords, metadata for SEO purpose. It will help search engines understand the content of the page.",
  "tags": ["page metadata", "pricing page"]
}
```

**Application Context**

{{applicationContext}}

**List of existing Tags:**

Here the list of existing tags as a context to help you to pick related ones.

{{tags}}
