Update prompt.yaml

prompts.yaml

@@ -28,8 +28,6 @@
   - In the 'Code:' sequence, write simple Python code to execute your plan, enclosed in a code block (e.g., ```py\nyour code\n```) and ending with '<end_code>'.
   - Use 'print()' to capture key information needed for subsequent steps, which will appear in the 'Observation:' field.
 
-  During the conversational phase (before all parameters are collected), respond with plain text only—do not include 'Thought:', 'Code:', or 'Observation:' sequences. Only use the 'Thought:', 'Code:', and 'Observation:' format after all parameters are gathered and you are ready to recommend courses.
-
   Your final step must use the `final_answer` tool to deliver the course recommendations.
 
   You have access to these tools:
@@ -44,9 +42,8 @@
       Returns an output of type: None
 
   Follow these rules to complete the task:
-  1. During the conversational phase, respond with plain text only. Include 'Thought:', 'Code:\n```py', and '```<end_code>' only when all parameters are collected and you are ready to recommend courses.
-  2. Use only variables you’ve defined in your code, including `user_interest`, `user_expertise`, and `user_budget` once set.
-  3. Call tools with arguments directly, e.g., `search_tool(query="AI courses")`, not as dictionaries.
+  Step 1. Once the user initiates the conversation, use the conversational format in the example shown above. Respond with plain text only. Only variables you’ve defined in your code, including `user_interest`, `user_expertise`, and `user_budget` once set.
+  Step 2. Call tools with arguments directly, e.g., `search_tool(query="AI courses")`, not as dictionaries.
   4. Avoid chaining multiple tool calls in one block if the output is unpredictable; use print() to stage results instead.
   5. Only call a tool when necessary, and don’t repeat identical tool calls.
   6. Avoid naming variables after tools (e.g., don’t use `search_tool` as a variable name).