[FEATURE] Regarding ToolSearch causing unnecessary multiple rounds of conversation

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I observed that in version 2.1.69, the default configuration of tools only includes ToolSearch. When only this tool remains, it causes any task startup to require multiple sessions to load Bash, Read, Edit, and Grep. These tools are frequently used and are involved in almost every session.
<img width="1248" height="838" alt="Image" src="https://github.com/user-attachments/assets/4c7598d0-f07a-46e9-be64-2dbe7f52cf42" />

Proposed Solution

I hope you can consider the priority of tools like Bash, Read, Edit, and Grep, or if you think there are other frequently used tools that need to be introduced in advance. I also have a question: although the Agent tool isn't called very often, I believe it's still important; should it also be considered for default release? ToolSearch should only be used with less frequently used tools.

Alternative Solutions

This significant change can be observed by examining the turn-based dialogue requests. While I also believe the context could be better optimized, I think the tools should prioritize different aspects. This is just a suggestion; perhaps you have better ideas. Thank you for your feedback!

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

At first, I only noticed that the startup requests were slower, so I discovered this pattern using a network packet capture tool. You can observe the first few requests to see if this commonality exists.

Additional Context

_No response_