> For the complete documentation index, see [llms.txt](https://docs.twtg.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twtg.io/docs/solidred-documentation/solidred-3.3/entity-management-features/annotations.md).

# Annotations

Annotations can be made on the overview of a machine or device by clicking on the **+** sign shown when hovering in the annotations section.&#x20;

On the pop-up screen, a title and a description of the annotation can be established. Click on the **Add annotation** button to add it to the machine.&#x20;

<figure><img src="https://content.gitbook.com/content/bvUukoXtbhsv9XV3KOU0/blobs/G1HKpy9DfwSusV9xs6Zy/image.png" alt=""><figcaption><p>Adding annotations</p></figcaption></figure>

Annotations can be seen on the machine overview screen and when adding annotations. Additionally, annotations can be removed by clicking on the expand icon in the entity overview and then clicking on the **X** in the top right corner of the annotation.

<figure><img src="https://content.gitbook.com/content/bvUukoXtbhsv9XV3KOU0/blobs/ZFKqKo0yozXfmOMd8kjU/image.png" alt=""><figcaption><p>Deleting annotations</p></figcaption></figure>


---

# 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.twtg.io/docs/solidred-documentation/solidred-3.3/entity-management-features/annotations.md?ask=<question>&goal=<user_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.
