docs(sdk): explain per-task LLM profile selection

AGENTS.md

@@ -77,7 +77,7 @@ mint dev
 Useful checks:
 
 ```bash
-mint broken-links
+mintlify broken-links
 ```
 
 ### Python tooling (sync/generation scripts)

sdk/guides/task-tool-set.mdx

@@ -133,10 +133,29 @@ When the parent agent calls the task tool, it provides these parameters:
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
 | `prompt` | `str` | Yes | The instruction for the sub-agent |
-| `subagent_type` | `str` | No | Which registered agent type to use (default: `"default"`) |
+| `subagent_type` | `str` | No | Which registered agent type to use (default: `"general-purpose"`) |
 | `description` | `str` | No | Short label (3-5 words) for display and tracking |
+| `llm_profile` | `str` | No | Saved LLM profile for this sub-agent; if omitted, it inherits the parent model |
 | `resume` | `str` | No | Task ID from a previous invocation to continue |
 
+## Selecting a Model for One Task
+
+Pass `llm_profile` to run a sub-agent on a [saved LLM profile](/sdk/guides/llm-profile-store) without changing the parent agent's model:
+
+```python icon="python"
+conversation.send_message(
+    "Use the task tool to implement this change with "
+    "subagent_type='general-purpose' and llm_profile='fast-worker'."
+)
+conversation.run()
+```
+
+For a sub-agent definition that inherits the parent model, `llm_profile` selects the worker model. Do not pass `llm_profile` when the selected sub-agent definition already specifies a model; the task returns a configuration error rather than silently choosing one.
+
+An unknown profile returns an error instead of silently using the parent model. When you resume a task with an inheriting definition, omitting `llm_profile` keeps the profile used by that task. Resuming with a model-pinned definition replaces the stored profile with the definition's model. Passing a different profile changes it for that resume and later resumes.
+
+The task tool shows the parent agent the names of profiles in the default profile store. It does not include profile configuration or credentials. If any registered sub-agent uses a custom `profile_store_dir`, the task tool omits the list rather than advertising names from a store that the selected agent may not use. You can still pass a valid profile name directly.
+
 ## Task Observation
 
 The tool returns a `TaskObservation` containing: