Clarify safe-outputs MCP tool invocation in workflow instructions

.github/workflows/daily-doc-updater.md

@@ -144,10 +144,11 @@ For each missing or incomplete feature documentation:
 If you made any documentation changes:
 
 1. **Summarize your changes** in a clear commit message
-2. **Use the `create_pull_request` tool** to create a PR
-   - **IMPORTANT**: Use the `create_pull_request` tool from safe-outputs to create the pull request
-   - Do NOT use GitHub API tools directly (like `create_pull_request` from the GitHub MCP server)
-   - The tool is automatically available because `safe-outputs.create-pull-request` is configured in the frontmatter
+2. **Call the `create_pull_request` MCP tool** to create a PR
+   - **IMPORTANT**: Call the `create_pull_request` MCP tool from the safe-outputs MCP server
+   - Do NOT use GitHub API tools directly or write JSON to files
+   - Do NOT use `create_pull_request` from the GitHub MCP server
+   - The safe-outputs MCP tool is automatically available because `safe-outputs.create-pull-request` is configured in the frontmatter
    - Call the tool with the PR title and description, and it will handle creating the branch and PR
 3. **Include in the PR description**:
    - List of features documented

.github/workflows/hourly-ci-cleaner.md

@@ -138,8 +138,7 @@ The CI workflow has failed on the main branch. Follow the instructions from the
 - **Verify quickly**: Re-run checks after fixes to confirm, then move on
 - **One issue at a time**: Only proceed to next step when current step passes
 - **Be concise**: Keep analysis brief and actionable
-- **Early termination**: If all checks pass, stop immediately and create PR
-- **Create a pull request with all fixes using the safe-outputs create-pull-request tool**
+- **Early termination & PR creation**: If all checks pass, stop immediately and **call the `create_pull_request` MCP tool from the safe-outputs server** to create a PR with all fixes
 
 **Token Budget Awareness:**
 - Aim to complete fixes within 15-20 conversation turns
@@ -149,7 +148,7 @@ The CI workflow has failed on the main branch. Follow the instructions from the
 
 ## Pull Request Guidelines
 
-After all fixes are completed and validated, **use the create-pull-request safe-output** to create a PR with your changes.
+After all fixes are completed and validated, **call the `create_pull_request` MCP tool** (from the safe-outputs MCP server) to create a PR with your changes.
 
 Your pull request should:
 - Have a clear title describing what was fixed (e.g., "Fix formatting and linting issues", "Fix test failures in pkg/cli")
@@ -161,13 +160,15 @@ Your pull request should:
 
 **To create the pull request:**
 1. Commit all your changes to a new branch
-2. Use the `create_pull_request` tool with:
-   - **Title**: Clear description of what was fixed
-   - **Body**: Detailed description including:
+2. **Call the `create_pull_request` MCP tool** (available through the safe-outputs MCP server) with:
+   - **title**: Clear description of what was fixed
+   - **body**: Detailed description including:
      - Summary of CI failures discovered
      - List of fixes applied (formatting, linting, test fixes, recompilation)
      - Confirmation that `make fmt`, `make lint`, `make test-unit`, and `make recompile` all pass
      - Link to the failed CI run that triggered this fix
    - The title will automatically be prefixed with "[ca] " as configured in safe-outputs
+
+**Important**: Do NOT write JSON to files manually. Use the MCP tool by calling it directly. The tool is available in your environment and will handle creating the pull request.
 
 Begin by checking out the main branch and running the CI cleaner steps.