> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/best-practices/set-titles-and-descriptions.md).
# Set Titles & Descriptions
Context can be crucial if other members of your team are looking at workflows. The following title does not give many contexts to the function of the workflow.
## Workflow Titles
Within your workflow, there is an option to adjust the title of each step. This is oh so helpful at placing a clear and purposeful title to each step. Your future self will thank you for adding a descriptive title so you won't have to dig into the details later.
Let's fix it! Click the title of your workflow or the **Dashboard** to bring up the **Manage workflow** details options to make changes.
Enter your new workflow name and select **Save Changes.** Whoa, this is a much better title!
## Workflow Descriptions
But wait, you can add more context! You can adjust the description in the **Manage workflow** details of your workflow. While you're updating that workflow name, in the same box find the **Description** field. The text can describe the goal, the steps, or anything else that is helpful to note.
Hit **Save Changes** and your new description will appear on the right-hand side of your workflow **Dashboard** page in the **Details** section.
## Step Titles
Within your workflow, there is an option to adjust the title of each step. This is oh so helpful at placing a clear and purposeful title to each step. Your future self will thank you for adding a descriptive title so you won't have to dig into the details later.
To add a new step title description, select the **Settings** section within the step. Next, add your updated or new title in the **Description** box and **Save**. Bravo, you have a descriptive title for your step!
---
# 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.getmesa.com/best-practices/set-titles-and-descriptions.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.