> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/definitions/why.md). # Why? **Why use the Definitions feature?**\ The Definitions feature helps you quickly navigate and manage all defined terms in your document, making drafting more efficient and accurate. **✅ When you *****should***** use it:** * **To speed up drafting**\ Instantly jump to any definition, saving time especially in long documents. * **To maintain consistency**\ Keep track of all definitions to make sure terminology is used consistently throughout the document. * **To improve document clarity**\ Ensure all key terms are clearly defined to avoid misunderstandings. *** **❌ When you *****shouldn’t***** use it:** * **If terms are defined outside the document**\ If definitions refer to external documents or agreements, this tool won’t catch those. * **If you need in-depth legal analysis**\ This feature highlights definitions but doesn’t replace a thorough legal review by a professional. --- # 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.clausebuddy.com/definitions/why.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.