> For the complete documentation index, see [llms.txt](https://help.maearth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.maearth.com/resources-for-land-stewards/organization-profile/organization-description.md).
# Organization Description
What makes a strong organization description?
Your organization description lets us know who you are, what you do, and who your collaborators are. Keep it clear and authentic.
A complete organization description might include the following:
#### Your origin story (1-3 sentences)
* Why was your organization created?
* What need or opportunity did you see?
* When did you start?
#### What you do (1-3 sentences)
* What kind of activities do you coordinate?
* What ecosystems or communities do you serve?
* What's your approach and why?
#### Your impact (1-2 sentences)
* How do you measure impact or change over time?
* By that measure, what have you accomplished so far?
*Suggested length: 150-300 words (\~2-3 short paragraphs)*
#### Organization profile example
"Kilifi Coastal Conservation was founded in 2020 when our local community of fishers noticed declining mangrove forests along our coastline. What started as weekend clean-ups has grown into a community movement restoring marine ecosystems.
We work with fishing communities, youth groups, and local government to protect and restore coastal wetlands. Our approach combines traditional ecological knowledge with mangrove science, training young people in restoration techniques while providing job opportunities.
So far, we've planted 5,000 mangrove trees across 3 hectares and trained 20 youth in restoration monitoring. Our vision is a thriving, biodiverse coastline where fishing communities can sustain themselves for generations to come."
#### Suggestions for writing your organization profile
* Be sure to define technical terms or acronyms
* Aim for specificity (numbers, places, plant names)
* Show a personal or community connection to the work
* Keep it genuine
---
# 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.maearth.com/resources-for-land-stewards/organization-profile/organization-description.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.
