Mode-Specific Tool Deactivation for Stability and Token Reduction

[SophusMaxiumus]

I propose adding the ability to selectively deactivate tools per model mode—via the GUI, .roomodes, or .roo/ folder files. This would control which tools are included in the system prompt for each mode, similar to how disabling MCP reduces prompt size.

Currently, the most effective approach is to move tool definitions into .roo/rules-*/tool-*.md and include only the relevant ones in the intended modes. However, this also requires overwriting the general system prompt for that specific mode to remove any related tool commands—a necessary but significant drawback.

Implementing this feature would:

• Significantly reduce token usage, especially when combined with orchestration tools like Orchiastrator.
• Improve task stability by avoiding interference from unrelated tools.
• Enforce strict tool boundaries, reducing context confusion and execution errors.

This would be a strong optimization for managing focused, efficient, and stable model modes.

[carlesso]

Isn't this a (partial) duplicate of #639?
Please see if my proposal make sense please.
Not sure about making it viable via UI.