> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/datafields/datafield-descriptions.md).

# Datafield descriptions

Descriptions can be used to add explanations or comments to datafields.

The user is free to include any description, comment or explanation in the description field so that the function of a description is completely up to the user (or the policy of the organisation).

For example in more complex clauses or concepts with many datafields, descriptions could be used to explain the exact role a datafield plays in a certain clause, document or library. This will make it much easier for any future user editing the datafield to understand its use, thereby avoiding the situation where any changes are made to the datafield that e.g. ‘break’ a clause (for example by removing predefines).


---

# 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://help.clause9.com/datafields/datafield-descriptions.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.