> 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/3.1/entity-management-features/entity-description.md). # Entity description The entity description can be added when adding either an asset or device in its respective field. Alternatively, the user can add an entity description in the edit screen for either [assets](/docs/solidred-documentation/3.1/entity-management-features/asset-management/edit-asset.md) or [devices](/docs/solidred-documentation/3.1/entity-management-features/device-management/edit-device.md). A final option is to add the description or edit it, in the Machine/Device overview page. Hovering over the description of the entity will allow the user to add a description by clicking on the plus icon if there's none. Type in the desired description and click the save button to update the description. If the user wishes to edit the entity's description, they can do so by clicking on the pencil icon available when hovering over the description in question. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.twtg.io/docs/solidred-documentation/3.1/entity-management-features/entity-description.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.