diff --git a/documentation/docs/guides/using-goosehints.md b/documentation/docs/guides/using-goosehints.md
index c85a69a4dc30..9dc517d96e8d 100644
--- a/documentation/docs/guides/using-goosehints.md
+++ b/documentation/docs/guides/using-goosehints.md
@@ -74,6 +74,8 @@ The `.goosehints` file can include any instructions or contextual details releva
 
 A good time to consider adding a `.goosehints` file is when you find yourself repeating prompts, or providing the same kind of instructions multiple times. It's also a great way to provide a lot of context which might be better suited in a file.
 
+Goosehints are loaded at the start of your session and become part of the system prompt sent with every request. This means the content of `.goosehints` contributes to token usage, so keeping it concise can save both cost and processing time.
+
 ## Setting up hints
 
 The `.goosehints` file supports natural language.
@@ -120,4 +122,4 @@ Like prompts, this is not an extensive list to shape your `.goosehints` file. Yo
 - **Keep file updated**: Regularly update the `.goosehints` file to reflect any changes in project protocols or priorities.
 - **Be concise**: Make sure the content is straightforward and to the point, ensuring Goose can quickly parse and act on the information.
 - **Start small**: Create a small set of clear, specific hints and gradually expand them based on your needs. This makes it easier to understand how Goose interprets and applies your instructions.
-
+**Reference other files**: Point Goose to relevant files like /docs/style.md or /scripts/validation.js to reduce repetition and keep instructions lightweight.
diff --git a/documentation/docs/mcp/memory-mcp.md b/documentation/docs/mcp/memory-mcp.md
index e2878998884f..5e0126ae64df 100644
--- a/documentation/docs/mcp/memory-mcp.md
+++ b/documentation/docs/mcp/memory-mcp.md
@@ -123,6 +123,11 @@ Later, you can ask:
 
 Goose will recall everything you’ve saved as long as you instruct it to remember. This makes it easier to have consistent results when working with Goose.
 
+Goose loads all saved memories at the start of a session and includes them in every prompt sent to the LLM. For large or detailed instructions, store them in files and instruct Goose to reference those files:
+
+> _Remember that if I ask for help writing JavaScript, I want you to refer to "/path/to/javascript_notes.txt" and follow the instructions in that file._
+
+
 ## Trigger Words and When to Use Them
 Goose also recognizes certain trigger words that signal when to store, retrieve, or remove memory.
 
@@ -243,4 +248,5 @@ If you frequently work with API standards or other structured knowledge, Goose m
     }
 
     Would you like me to implement the full endpoint logic?
-    ```
\ No newline at end of file
+    ```
+