Skip to content

Response Formatting Instructions Mixed Into Tool Descriptions #9310

@shanevcantwell

Description

@shanevcantwell

Before submitting your bug report

Relevant environment info

- OS: any
- Continue version: 1.3.28 (verified against main branch)
- IDE version: any
- Model: any (all models receive conflicting instructions)
- config: any

Description

Response Formatting Instructions Mixed Into Tool Descriptions

Summary

Tool descriptions contain instructions about how to format response text, which conflates "how to use this tool" with "how to write your response."

Example

runTerminalCommand.ts:30:

"When suggesting subsequent shell commands ALWAYS format them in shell command blocks."

This instruction is about formatting the assistant's prose response, not about how to call the run_terminal_command tool.

The Problem

  1. Separation of concerns: Tool descriptions should describe the tool's purpose and parameters, not response formatting
  2. Maintenance: Formatting preferences are scattered across tool definitions instead of centralized
  3. Confusion: Models may interpret this as a tool-calling instruction rather than a formatting preference

Proposed Fix

Move response formatting instructions to the base system message or a dedicated formatting section, keeping tool descriptions focused on:

  • What the tool does
  • What parameters it accepts
  • When to use it vs alternatives
  • Any constraints or limitations

Affected Tools

  • run_terminal_command - "ALWAYS format them in shell command blocks"
  • Potentially others with similar mixed concerns

To reproduce

No response

Log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:toolsRelates to tool usage

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions