improve instructions

Author: kentcdodds

exercises/03.resources/01.problem.simple/README.mdx

@@ -1,17 +1,21 @@
 # Resources
 
-👨‍💼 Our users really want to know who's responsible for building this amazing
-app! (That's you!). In this step, you'll take your first step toward exposing
-structured data from your server—not just as tool responses, but as first-class
-resources that clients can discover and read.
+👨‍💼 Our users really want to include their tags in the context as they write
+their journal entries. They could just ask the LLM to run the `list_tags` tool,
+but that's not as efficient. In fact, the host application they're using could
+proactively request the resources we expose without any input from the user as
+well. Making it both efficient and convenient for the user.
+
+In this step, you'll take your first step toward exposing structured data from
+your server—not just as tool responses, but as first-class resources that
+clients can discover and read.
 
 Your goal:
 
 - Declare the `resources` capability on your server.
-- Register a simple resource called "credits" that provides information about
-  the creator of the app. This resource should be available at the URI
-  `epicme://credits` and return a plain text string with the username of the app's
-  creator.
+- Register a simple resource called "tags" that provides information about all
+  the tags in the database. This resource should be available at the URI
+  `epicme://tags` and return a JSON array of tags.
 
 This is your first taste of the MCP resources system. No need for dynamic
 templates or database integration yet—just get a static resource registered and

exercises/03.resources/02.problem.template/README.mdx

@@ -48,6 +48,13 @@ Notice how the `list` callback queries the database and returns a resource
 listing for each name. This pattern is exactly what you'll use to expose entries
 and tags from your own database.
 
+<callout-success>
+	The reason for the `list` callback is to make it easy for clients to get a
+	list of available resources without having to know the exact URIs and without
+	having to request the entire resource (notice we only return the name, URI,
+	and type in the `list` callback).
+</callout-success>
+
 Your goal in this step:
 
 - Use resource templates to expose entries and tags from your database, each