> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/readme/content/annotations/edit-annotations.md).
# Edit annotations
Move and resize annotations as needed in your reports.
### Move annotations
1. To move an annotation, hover over it with your mouse until the cursor changes to a crosshair style. \
2. Click, drag, and drop the annotation to a new location on the image.
### Resize annotations
1. To resize an annotation, hover over it with your mouse until the cursor changes to a double-sided arrow. Click and drag the annotation to the desired size.\
2. Lines can be resized by clicking on either end of the annotation and dragging to the desired length. \
3. Similarly, polygons can be resized by clicking on a corner of the image and dragging to adjust the shape. \
{% hint style="info" %}
When resizing lines and polygons, the cursor remains in the crosshair style.
{% 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.reportandrun.com/manual/readme/content/annotations/edit-annotations.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.