Optimize default prompts to significantly reduce tokens usage.

ac_mode_and_fan_control_full_llm.yaml

@@ -75,46 +75,36 @@ blueprint:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify at least one air conditioner name to control.
-            To control multiple ACs, separate each name with a semicolon.
+            Mandatory. Provide AC names to control. Use semicolons (;) to separate multiple names.
         hvac_mode_prompt:
           name: HVAC Mode Prompt
           description: The prompt which will be used for the LLM can provide the AC mode.
           selector:
             text:
               multiline: true
           default: |-
-            Use this argument to set the AC mode. Accepted values: auto, cool, heat, dry, fan_only, off.
-            Include this only when the user explicitly requests a mode change; otherwise omit it.
-            If the requested mode is not in the device's supported modes, return an error instead of guessing or changing another field.
+            Set AC mode (auto, cool, heat, dry, fan_only, off). Include ONLY if explicitly requested. Return error if unsupported; do not guess.
         temperature_prompt:
           name: Temperature Prompt
           description: The prompt which will be used for the LLM can provide the target temperature.
           selector:
             text:
               multiline: true
           default: |-
-            Use this argument to set the target temperature. Input should be a number (e.g., 24, 25.5).
-            Ensure the number matches the device's unit system (usually Celsius). If the user provides Fahrenheit for a Celsius device, convert it first.
-            Do not include units like 'C' or 'F'.
-            Include this only when the user explicitly requests a temperature change.
+            Target temperature as a number (e.g. 24). Convert F to C if needed. Omit units (C/F). Include ONLY for explicit requests.
         fan_mode_prompt:
           name: Fan Mode Prompt
           description: The prompt which will be used for the LLM can provide the fan speed/mode of the AC.
           selector:
             text:
               multiline: true
           default: |-
-            Use this argument to set the AC's fan mode (fan speed). Accepted examples: auto/automatic, low/1, lowmid/2, mid/medium/3, highmid/4, high/5.
-            Map qualitative or numeric requests to the closest matching supported mode; resolve per device when multiple ACs are targeted.
-            Include this only when the user requests a fan speed change; otherwise omit it.
-            If no supported fan mode matches for a device, return an error instead of guessing or changing another field.
+            Set fan speed (auto, low/1, lowmid/2, mid/3, highmid/4, high/5). Map to the closest supported mode. Include ONLY if requested. Error if no match; do not guess.
 mode: parallel
 max_exceeded: silent
-description: Controls the mode, temperature, and/or fan speed of one or more specified air conditioners.
+description: Controls mode, temperature, and fan speed for air conditioners. Supports auto, cool, heat, dry, and fan_only modes.
 variables:
-  version: 20251213
+  version: 20260207
 fields:
   ac_entities:
     name: AC Entities

advanced_google_search_full_llm.yaml

@@ -56,23 +56,20 @@ blueprint:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify the search string to obtain information from Google.
-            If the query seems misspelled or misheard, silently correct it to the most likely intended search string and proceed. Do not ask clarifying questions; instead, briefly note the correction in the response.
+            Mandatory. Search query. Silence-correct misspellings if likely intended. Do not ask for clarification.
         language_prompt:
           name: Language Prompt
           description: The prompt which will be used for the LLM can provide the language for the query.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify the output language of the response using an IETF BCP 47 language tag (e.g., vi-VN, en-US). The value must match the user's language.
+            Mandatory. Language tag (e.g. vi-VN, en-US). Must match user language.
 mode: parallel
 max_exceeded: silent
-description: Searches Google based on a query string.
+description: Searches Google to retrieve real-time information, facts, or answers from the web. Use when local knowledge is insufficient.
 variables:
-  version: 20251116
+  version: 20260207
 fields:
   query_string:
     name: Query String

advanced_youtube_search_full_llm.yaml

@@ -71,25 +71,20 @@ blueprint:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify the search string to obtain a list of videos.
-            If the query contains errors caused by user mispronunciation, correct it to the most likely accurate search string and ask the user for confirmation before proceeding.
-            After obtaining the results, prompt the user to select a video to play on the TV. Add an ordinal number to each video to simplify selection. Do not include the Media ID in the response.
+            Mandatory. Search query. Silence-correct misspellings. For results, use ordinal numbers for selection; omit Media IDs. Confirm before proceeding if query is ambiguous.
         page_token_prompt:
           name: Page Token Prompt
           description: The prompt which will be used for the LLM can provide the page token to get additional videos that could be obtained.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is optional.
-            Specify the page token to obtain additional videos.
-            Use it when the initial query results are unsatisfying and the user wants to find more videos.
+            Optional. Use to fetch more videos if initial results are unsatisfactory.
 mode: parallel
 max_exceeded: silent
-description: Searches YouTube for videos based on a query string.
+description: Searches YouTube for videos and returns a list of matching results with titles and descriptions. Use to find specific content or playlists.
 variables:
-  version: 20251116
+  version: 20260207
 fields:
   query_string:
     name: Query String

calendar_events_lookup_full_llm.yaml

@@ -51,45 +51,36 @@ blueprint:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Use 'daily' for requests covering full days or periods longer than one day. Use 'hourly' for requests covering part of a day or a specific start time.
-            After obtaining the result, ensure the response includes only the event's day of the week and start date. The event's end date or time is exclusive and should not be included.
+            Mandatory. 'daily' for full days/long periods; 'hourly' for partial days/specific times. Response must only include day of week and start date.
         time_period_length_prompt:
           name: Time Period Length Prompt
           description: The prompt which will be used for the LLM can provide the length of the period.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            The length of the period. This will be measured in days if 'time_period_type' is 'daily', and in hours if 'time_period_type' is 'hourly'.
-            Examples: 1 (day) for today's events, 2 (days) for weekend events, 7 (days) for the next few days, 30 (days) for in the month, 6 (hours) for morning, afternoon, or evening events.
+            Mandatory. Length in days (if daily) or hours (if hourly). E.g. 1 (today), 7 (week), 6 (afternoon).
         date_prompt:
           name: Date Prompt
           description: The prompt which will be used for the LLM can provide the start date for the events period.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify the date for the requested period starts using the format YYYY-MM-DD.
-            Always include a date with each request. If the request does not specify a date, you should provide today's date. Examples of dates that can be used include today, this week, this month, etc.
-            When the requested period is for the night, do not use today's date but always use the next day, unless the current time is still before 05:00:00.
+            Mandatory. Start date (YYYY-MM-DD). Default to today if unspecified. For "night", use next day unless current time < 05:00:00.
         time_prompt:
           name: Time Prompt
           description: The prompt which will be used for the LLM can provide the start time for the events period.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify the start time using the format HH:MM:SS.
-            Always provide time. For a full day, use 00:00:00. For the current hour, use the start of the hour. Night starts at 00:00:00, morning starts at 06:00:00, afternoon starts at 12:00:00 and evening starts at 18:00:00.
+            Mandatory. Start time (HH:MM:SS). Full day = 00:00:00. Morning = 06:00:00, Afternoon = 12:00:00, Evening = 18:00:00, Night = 00:00:00.
 mode: parallel
 max_exceeded: silent
-description: Retrieves calendar events based on specified time periods.
+description: Retrieves upcoming or past calendar events for a specific time period. Useful for checking schedules and appointments.
 variables:
-  version: 20251116
+  version: 20260207
 fields:
   time_period_type:
     name: Time Period Type

camera_snapshot_full_llm.yaml

@@ -100,16 +100,12 @@ blueprint:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify the friendly name of the camera you want to capture a snapshot from (e.g., "Front Door Camera").
-            If the user's request does not clearly specify a camera, determine and suggest one or more relevant cameras based on context.
-            If multiple cameras are needed, submit each camera in a separate tool call.
-            The tool will return a local file path to the generated snapshot.
+            Mandatory. Camera friendly name. If unclear, determine from context or suggest. For multiple cameras, use separate tool calls. Returns local image path.
 mode: parallel
 max_exceeded: silent
-description: Captures a snapshot from a specified camera to visually check the scene. Returns the local file path of the image, which can be used by other tools for analysis or sent to the user.
+description: Captures and saves a camera snapshot. Returns the local file path for analysis or messaging tools. Useful for visual verification of a scene.
 variables:
-  version: 20251209
+  version: 20260207
 fields:
   camera_name:
     name: Camera Name

create_calendar_event_full_llm.yaml

@@ -58,76 +58,58 @@ blueprint:
       input:
         summary_prompt:
           name: Summary Prompt
-          description: The prompt which will be used for the LLM can provide the short summary or subject for the event.
+          description: Short summary of the event.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            It defines the short summary or subject of the event.
+            Mandatory. Subject or title of the event.
         description_prompt:
           name: Description Prompt
-          description: The prompt which will be used for the LLM can provide a more complete description of the event than the one provided by the summary.
+          description: Detailed description of the event.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is optional.
-            It provides a more complete description of the event than the summary.
+            Optional. Full details of the event.
         start_date_time_prompt:
           name: Start Time Prompt
-          description: The prompt which will be used for the LLM can provide the date and time the event should start.
+          description: Start date and time for timed events.
           selector:
             text:
               multiline: true
           default: |-
-            Use either the start_date_time parameter or the start_date parameter, but not both.
-            This argument specifies the event start date and time in the format YYYY-MM-DD HH:MM:SS.
-            Only populate start_date_time when the request includes a time-of-day (e.g., 10:00, 18:30, morning/afternoon/evening). Otherwise use start_date.
-            When using start_date_time (timed events), you must also provide end_date_time. Do not provide end_date.
-            If the user does not specify an end time, you must still provide end_date_time = start_date_time + 2 hours. Do not ask clarifying questions.
+            Use ONLY for timed events (YYYY-MM-DD HH:MM:SS). Excludes start_date.
         end_date_time_prompt:
           name: End Time Prompt
-          description: The prompt which will be used for the LLM can provide the date and time the event should end.
+          description: End date and time for timed events.
           selector:
             text:
               multiline: true
           default: |-
-            Use either the end_date_time parameter or the end_date parameter, but not both.
-            This argument specifies the event end date and time in the format YYYY-MM-DD HH:MM:SS.
-            For timed events, you must provide end_date_time and it must be on or after start_date_time.
-            Do not provide end_date when start_date_time is used.
-            If the user did not specify an end time, infer and provide end_date_time = start_date_time + 2 hours. Do not ask clarifying questions.
+            Mandatory for timed events. Default: start + 2h. Excludes end_date.
         start_date_prompt:
           name: Start Date Prompt
-          description: The prompt which will be used for the LLM can provide the date the all-day event should start.
+          description: Start date for all-day events.
           selector:
             text:
               multiline: true
           default: |-
-            Use either the start_date parameter or the start_date_time parameter, but not both.
-            This argument specifies the start date of an all-day event in the format YYYY-MM-DD.
-            Use start_date for date-only requests (no time-of-day mentioned).
-            When using start_date (all-day events), you must also provide end_date. Do not provide end_date_time.
-            If the user does not specify an end date, you must still provide end_date = start_date + 1 day. Do not ask clarifying questions.
+            Use ONLY for all-day events (YYYY-MM-DD). Excludes start_date_time.
         end_date_prompt:
           name: End Date Prompt
-          description: The prompt which will be used for the LLM can provide the date the all-day event should end.
+          description: End date for all-day events.
           selector:
             text:
               multiline: true
           default: |-
-            Use either the end_date parameter or the end_date_time parameter, but not both.
-            This argument specifies the end date of an all-day event in the format YYYY-MM-DD.
-            For all-day events, you must provide end_date and it must be on or after start_date.
-            Do not provide end_date_time when start_date is used.
-            If the user did not specify an end date, infer and provide end_date = start_date + 1 day. Do not ask clarifying questions.
+            Mandatory for all-day events. Default: start + 1 day. Excludes end_date_time.
 mode: queued
 max: !input simultaneous
 max_exceeded: silent
-description: Creates a new calendar event with specified details.
+description: Adds a new event to a specified calendar. Handles both timed and all-day events with mandatory start/end details.
 variables:
-  version: 20251116
+  version: 20260207
 fields:
   summary:
     selector:

date_lookup_and_conversion_full_llm.yaml

@@ -48,35 +48,28 @@ blueprint:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            It must be one of the following two values: 's2l' to convert a Solar date to a Lunar date, or 'l2s' to convert a Lunar date to a Solar date.
-            After obtaining the result, ensure the response clearly specifies the day of the week, the Solar date, the Lunar date, and the number of days remaining or days elapsed.
+            Mandatory. 's2l' (Solar to Lunar) or 'l2s' (Lunar to Solar). Response must include: day of week, both dates, and days remaining/elapsed.
         date_prompt:
           name: Date Prompt
           description: The prompt which will be used for the LLM can provide the input date for the conversion.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is mandatory and must always be included.
-            Specify the date for the requested conversion using the format YYYY-MM-DD.
-            Always include the relevant date: today's date for today's request, tomorrow's date for tomorrow's request.
-            If the request does not specify a year, assume the current year.
+            Mandatory. Date (YYYY-MM-DD). If year unspecified, use current year. Use today/tomorrow as needed.
         leap_month_prompt:
           name: Leap Month Prompt
           description: The prompt which will be used for the LLM can provide the leap month for the conversion.
           selector:
             text:
               multiline: true
           default: |-
-            This argument is optional.
-            Use this argument only when converting Lunar dates to Solar dates.
-            It must be one of the following two values: 'true' for a leap month, or 'false' for a regular month.
+            Optional for l2s. 'true' for leap month, 'false' for regular. Do not use for s2l.
 mode: parallel
 max_exceeded: silent
-description: Converts dates between Solar and Lunar calendars, looks up auspicious/inauspicious days according to East Asian traditions, and determines the day of the week for any given date.
+description: Converts dates between Solar and Lunar calendars, looks up auspicious days, and determines the day of the week.
 variables:
-  version: 20251116
+  version: 20260207
 fields:
   conversion_type:
     name: Conversion Type