> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/labeling/labeling-tools/tools/message.md).
# Message
Overview of the Message labeling tool in Ango Hub
The Message labeling tool is used to classify individual messages in [LLM Chat assets](/data/importing-assets/creating-and-importing-llm-chat-assets.md) in the [LLM Chat labeling editor](/labeling/labeling-editor-interface/llm-chat-labeling-editor.md).
{% hint style="info" %}
The Message tool is supported across the LLM Chat labeling editor.
{% endhint %}
## How to add a Message tool to your project
From the project’s *Settings* tab, enter the *Label Set* section.
Click on *Add Category*. From the list that appears, click on *Message*.
A new row will appear named *Message*. Click on it to expand it.
Give your message tool a title.
Enable the *Required* toggle if you want to force labelers to classify at least one message. When the toggle is disabled, labelers will be able to save and move to the next asset without classifying a message using this class.
In order to ask labelers questions about the individual message, for example, if you want to show a further *radio* after placing the message-type class, you must click on *Add Classification* and add a further question. [More on nested questions here](/labeling/labeling-tools/tools/nested-classifications.md).
## How to Label a Message
From the *Tools* section on the left sidebar, select a *Message* labeling tool, then click on the message you would like to classify.
The nested classifications of the class will appear on the right-hand side of the screen. Answer the questions to classify the message.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.imerit.net/labeling/labeling-tools/tools/message.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
