feat: Improved per chat tool toggles

Before Submitting

• I searched open and closed issues and discussions for an existing request.
• I checked whether this already exists on the dev branch or latest source.
• I understand that maintainers want a well-written issue or discussion before any code pull request.
• This request is not a security vulnerability.

Problem

Models support tools well but sometimes they get confused by exposed tools or use them when it isn't necessary for a task:

• Unnecessary tool calls slow down responses
• Confuse the model having it go off on some weird tangent

Here is an example:

There are already toggles for Image, Code Interpreter and Web Search.
Which are all great.
Although Image should be renamed to Image Generation as image attachment always works if I understand that correctly.
I would like to see a Knowledge toggle to enabled/disable all knowledge tools.

Another issue is the current ui which scales poorly with more tools in that menu:

If more were to be added there would be a lot of noise in the ui.

Desired Behavior

As a user I would like more granular control over which tools are exposed to the model.
This especially applies to Knowledge tools.

Also a number similar to the example would be better than spamming blue bubbles.

Why This Matters

It would help steer weaker models in the direction I want them in.
It allows users to evaluate native capabilities of the model.
It improves performance for simple queries where models sometimes explore knowledge bases when it isn't necessary.
It could also impact costs as it may keep token usage more manageable.

A per chat setting is best for this. The current options are too broad and impact all users.

Examples or References

Here is how openrouter.ai does it for example:

Discussion: #29491

Alternatives or Workarounds

My main use would be to opt out of knowledge tools per chat.
The current workaround is to opt all models out of tool use which impacts all users.
Alternatively tool mode can be set to legacy which also impacts all users and is a legacy setting which I'd rather not depend on.

Start by reviewing the existing per-chat Image, Code Interpreter, and Web Search toggles, then read Discussion #29491 for related context. Done means users can control Knowledge tools per chat, the Image label is clarified, and the tool menu remains usable as more options are added.