docs: add groups to modelspecs (#429)

Co-authored-by: Dustin Healy <[email protected]>

Author: pnancarrow

pages/docs/configuration/librechat_yaml/object_structure/model_specs.mdx

@@ -199,7 +199,7 @@ URL or a predefined endpoint name for the model's icon.
   ]}
 />
 
-**Description:**  
+**Description:**
 A brief description of the model and its intended use or role, shown in the header dropdown menu.
 
 ---
@@ -208,41 +208,59 @@ A brief description of the model and its intended use or role, shown in the head
 
 <OptionTable
   options={[
-    ['group', 'String', 'Optional field to organize model specs in the UI selector with flexible grouping.', 'No default. Optional.'],
+    ['group', 'String', 'Optional group name for organizing model specs in the UI selector. Controls where the spec appears in the menu hierarchy.', 'No default. Optional.'],
   ]}
 />
 
-**Description:**  
-Optional group name for organizing specs in the UI selector. The behavior depends on the `group` value:
+**Description:**
+Optional group name for organizing model specs in the UI selector. The `group` field provides flexible control over how model specs are organized:
 
-- **Endpoint name** (e.g., "openAI", "groq"): If `group` matches an existing endpoint name, the spec appears nested under that endpoint in the UI
-- **Custom name**: If `group` is a custom string that doesn't match any endpoint, it creates a separate collapsible section with that name
-- **Omitted**: If `group` is not specified, the spec appears as a standalone item at the top level
+- **If `group` matches an endpoint name** (e.g., `"openAI"`, `"groq"`): The model spec appears nested under that endpoint in the selector menu
+- **If `group` is a custom name** (doesn't match any endpoint): Creates a separate collapsible section with that name
+- **If `group` is omitted**: The model spec appears as a standalone item at the top level
+
+This feature is particularly useful when you want to add descriptions to models without losing the organizational structure of the selector menu.
 
 **Example:**
-```yaml filename="modelSpecs / group"
+
+```yaml filename="modelSpecs with group field examples"
 modelSpecs:
   list:
-    # Nested under openAI endpoint
-    - name: "gpt-4o-custom"
+    # Example 1: Nested under an endpoint
+    # When group matches an endpoint name, the spec appears under that endpoint
+    - name: "gpt-4o-optimized"
       label: "GPT-4 Optimized"
-      group: "openAI"  # Matches endpoint name
+      description: "Most capable GPT-4 model with multimodal support"
+      group: "openAI"  # Appears nested under the OpenAI endpoint
       preset:
         endpoint: "openAI"
         model: "gpt-4o"
-    
-    # Custom group section
+
+    # Example 2: Custom group section
+    # When group is a custom name, it creates a separate collapsible section
     - name: "coding-assistant"
       label: "Coding Assistant"
-      group: "my-assistants"  # Custom group
+      description: "Specialized for coding tasks"
+      group: "my-assistants"  # Creates a custom "my-assistants" section
       preset:
         endpoint: "openAI"
         model: "gpt-4o"
-    
-    # Standalone at top level
+
+    # Multiple specs with the same group name are grouped together
+    - name: "writing-assistant"
+      label: "Writing Assistant"
+      description: "Specialized for creative writing"
+      group: "my-assistants"  # Grouped together with coding-assistant
+      preset:
+        endpoint: "anthropic"
+        model: "claude-sonnet-4"
+
+    # Example 3: Standalone (no group)
+    # When group is omitted, the spec appears at the top level
     - name: "general-assistant"
       label: "General Assistant"
-      # No group field - appears at top level
+      description: "General purpose assistant"
+      # No group field - appears as standalone item at top level
       preset:
         endpoint: "openAI"
         model: "gpt-4o-mini"