> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/psychology/availability-heuristic.md).
# Availability Heuristic
People overestimate the likelihood of events that are easily recalled from memory.
The Availability Heuristic is a mental shortcut that our brains use to make decisions quickly. It's based on the idea that if something comes to mind easily, we tend to think it's more common or important.
For example, if you've recently heard a lot about shark attacks in the news, you might think they happen all the time, even though they are quite rare.
This heuristic can lead to biases in our thinking because it relies on what's readily available in our memory rather than a more accurate assessment of the actual frequency or probability of events.
#### Further Reading
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
#### Further Viewing
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/psychology/availability-heuristic.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.
