> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/events/sign-up-for-an-event/how-to-leverage-the-event-or-series-descriptions.md). # How to leverage the Event or Series descriptions * When creating an Event or Series, whether it’s an Open Play, Tournament, League, or Clinic, it’s valuable to leverage the descriptions. * Your Customers will view the Event descriptions when they sign up, so this is the space where you can detail the type of Event, event provide information that is necessary for each Customer to know before arriving at the Event. This is the space where you can also inform your Customers of the different Event price between Members and Non-members. * You can use Markdowns in the Event description copy, like creating headers and sub-headers, highlighting, quoting, bolding, italicizing, underlining, and even creating alerts. The video below showcases how to use the description copy for a Series. {% embed url="" %} --- # 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.podplay.app/events/sign-up-for-an-event/how-to-leverage-the-event-or-series-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.