improve instructions

Author: kentcdodds

exercises/02.tools/README.mdx

@@ -16,6 +16,16 @@ In the future, hopefully we can even respond with UI! For more on this, check
 out my post
 [The future of AI interaction: Beyond just text](https://www.epicai.pro/the-future-of-ai-interaction-beyond-just-text-w22ps).
 
+<callout-success>
+	From [the MCP
+	Spec](https://modelcontextprotocol.io/specification/2025-03-26/server/tools):
+	Tools in MCP are designed to be **model-controlled**, meaning that the
+	language model can discover and invoke tools automatically based on its
+	contextual understanding and the user's prompts. However, implementations are
+	free to expose tools through any interface pattern that suits their needs—the
+	protocol itself does not mandate any specific user interaction model.
+</callout-success>
+
 {/* Mermaid diagram: https://simple-mermaid.netlify.app?d=M4UwjgriB2DGIBECWBDA5gJxQWwFAAJD8AHFDAFyViVOnPwGEAbJGcgo0iqmlO-AMogMAN2EdCzVnQC0APjlDRwgFz4AUgIDyAORkAlAAoN8+8FGD0A3gCJsIcgAsA9gBMbam+WfOmwAPSwKExMNgA0+DZcOMAe+LbQOCBxNo4gIc7hkWRoEPZ0sWpWAL6lEoLCYhgy8nJSbGqaugbGpiDAxM7QoPE2GO0QTORxtrBd5GxxANq25ACexMmeEwAewxFeIGspABLpTM4RAO7OGEyuAIQ2xQC6pUA */}
 
 <div

exercises/03.resources/README.mdx

@@ -12,6 +12,16 @@ with clients—such as files, database entries, or application metadata—using
 uniform interface. Each resource is uniquely identified by a URI and can be
 described with metadata like a name, description, and MIME type.
 
+<callout-success>
+	From [the MCP
+	Spec](https://modelcontextprotocol.io/specification/2025-03-26/server/resources):
+	Resources in MCP are designed to be **application-driven**, with host
+	applications determining how to incorporate context based on their needs.
+	However, implementations are free to expose resources through any interface
+	pattern that suits their needs—the protocol itself does not mandate any
+	specific user interaction model.
+</callout-success>
+
 Here's what this user experience may feel like.
 
 {/* Mermaid diagram: https://simple-mermaid.netlify.app?d=M4UwjgriB2DGIBECWBDA5gJxQWwFAAJD8AHFDAFyViVOnPwFVQMCjSKqaU78BBY4q0LtK1WvQAyEgLJCSZUVx4BhADZIY5OSM7j8AZRAYAbkblMjAWgB81-sQBc+AErgoweuQD2+YxoDu+BggwF4QGPDAcvY21moadE4SSB5BIWERIfgAFCAAdGh5ADT4mhgawAD05OjAAJRy8ZqxhiZGTsGh4ZGV6h5yraYYlrFNifjJqV4AZmldmcA5DM4AksAl2CA1ACYoNQ1E+GPkI7b2SSn0M3MZkdECp9YWGE76ABZegSjGKEiqKAAjVQgG7dELmZixc4GEDA2D0Tq3EHeXwBe7EUbqTROVwobagzKNLF0FpGIYddJgqrBPE5fxIchvRirA5EQZWTEJcg4ymZfCwLx0TSLbK7GobLZ4vYoVmEY6PaGuebwfmC8jC9GPZ5OZDAYj-ACeBJVYpQcgAcl51fgvEM+AIiuyXvgACpeLyqObEQWgRawbilbAAkD4xFgtLTIwwSL4aZeDBBKhvIyqoUAD3IQA */}

exercises/04.prompts/README.mdx

@@ -15,6 +15,18 @@ or "review this code"), each with a clear description and customizable
 arguments. This enables richer, more user-driven interactions, where clients can
 select and fill in prompts as needed.
 
+<callout-success>
+	From [the MCP
+	Spec](https://modelcontextprotocol.io/specification/2025-03-26/server/prompts):
+	Prompts are designed to be **user-controlled**, meaning they are exposed from
+	servers to clients with the intention of the user being able to explicitly
+	select them for use. Typically, prompts would be triggered through
+	user-initiated commands in the user interface, which allows users to naturally
+	discover and invoke available prompts. However, implementors are free to
+	expose prompts through any interface pattern that suits their needs—the
+	protocol itself does not mandate any specific user interaction model.
+</callout-success>
+
 Here's an example of how the user experience might look:
 
 {/* Mermaid diagram: https://simple-mermaid.netlify.app?d=M4UwjgriB2DGIBECWBDA5gJxQWwFAAJD8AHFDAFyViVOnPwFVQMCjSKqaU78BBY4q0LtK1WvQAyEgLJCSZUVx4BhADZIY5OSM7j8AZRAYAbkblMjAWgB81-sQBc+APLEYJDAHtsxethgQcvY21moadE4ASuBQwPQoxihIqigARqogHt6+wHJhmiGGJkZOEkhxWT7kuUQGRqYYliH5EfgACl5VwPjqcXnqBSH2Th3Z1T3lWrXBIRYYTvoAFp4A7pU55sxDAgsgGbD0xJ2++ABkWcZIACaZZGgQ-nQ1RMG2LeROAOIgh8f05CAfCkAf1wuRCvUSvhvr8xvgAUCUCDakUGk03gNWqMqvDAcRgSBQYNbMN2n9cYjkS8BCEpNInAAxZKqdb0c5IaDGTwAa0JtTp6LsOzJcP8wGA6BA3QAFHEMBADhAMCArgBKII02bMBbLNZ0-DK4DETzQUBAA */}