# Token Anatomy - Description

## Token Anatomy - Description

The `description` of a Design Token can be used to define additional details, like ***why*** or ***how*** we made this decision. The `description` is optional. 

<figure><img src="/files/U7OE8yxAzNmOVXRQfc0Z" alt=""><figcaption><p>In this infographic, the Token examples on the right side highlight the Description. Only the bottom example has a description. </p></figcaption></figure>

### Description = Additional context when needed

You can think of a Token's **description** as a place to add a note or reminder about this design decision for your engineers or future self.

For example, a Font Family Token may have a description with a link to download the files.

<figure><img src="/files/hHIYubO68idbtBdJNPVg" alt=""><figcaption><p>An infographic example of documenting a Font Family Token with a Description that includes a note and URL to download the Font.</p></figcaption></figure>

### Descriptions are meta-data shared across tools and technologies.

Descriptions are technically meta-data, so the `description` is available anywhere a Token is utilized. Engineers can view the description in code and design tools often add the `description` to token properties.&#x20;

For example, if a brand color is bright and vibrant it may have limited use cases. Any constraints can be added to the `description` in the Token as below.&#x20;

> *Only use for brand logo and branded illustrations as this lime green is not accessible for interactive elements.*

When that Token is attached to a color style in Figma, the `description` is visible to designers using Figma's native UI.&#x20;

The additional context you can add to the `description` of a Token helps cross-functional team members understand ***why*** or ***how*** they might use these design decisions in their own work.&#x20;

***

### Up next - Name

Next, let's explore the `name` of a Design Token as this anatomic property often provides an indication of design decisions that are detailed in the `description` .&#x20;

<figure><img src="/files/knDQKho3v0YWcQvsZx7s" alt=""><figcaption><p>In this infographic, the Token examples on the right side highlight the Name. The top code block shows a Token Name with groups. The bottom code block shows a flat Token Name.</p></figcaption></figure>

<div data-full-width="true"><figure><img src="/files/qSME9uW0VNGhe2MkT9FL" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tokens.studio/fundamentals/design-tokens/anatomy-description.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.