> 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/3d-multi-sensor-fusion/labeling/instruction.md).
# Instruction
A dedicated UI where the Project Owners and [Managers](https://docs.imerit.net/labeling/managing-users-in-projects#managers) can add labeling instructions, in PDF format to the on-going project. This intruction document is available from the tool for the labellers to access.
## Adding Instruction
These instructions are then available to see to anyone who can access the project, and are viewable on the next browser tab from the labeling editor.
## View on Tool
1. Launch the 3D MSF tool and on the top-right corner, click on help i.e. '?'
2. Select Instructions from the drop down
3. Instructions model will appear, click on the attached PDF
The attachment will open in the next tab for reference.
{% hint style="info" %}
If instructions have already been uploaded, the user can replace them by clicking on *Upload Instructions*.
{% endhint %}
---
# 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/3d-multi-sensor-fusion/labeling/instruction.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.
