System tools unfairly count against user token limits

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

this is kind of absurd.
Im paying for a service, and then I am being charged 15k tokens (7.5% of context) for tools that should honestly be part of the core functionality. Thats like a mechanic charging you rent for their wrench.
System tools shouldn't count toward my token context they re not optional extras, they're essential for Claude to even function. Without Read/Write/Edit, it can't handle files; without Bash, it cant run commands.
The MCP tools (15.7k) are at least optional — I set those up myself. But the system tools? They're basic equipment.
Some users already struggle with context limits, and this adds another unnecessary layer. The recent update feels unfair to those already working within tight constraints.
I don't charge you for Claude using my terminal either, but that would be fair, right? 😉 -

Thx, Stay healthy

Proposed Solution

1. Cache frequently used tools: After first use in a session, don't reload tool definitions?
2. Execute basic file operations locally without token overhead
3. Only load tool definitions when actually needed, not all 15k tokens upfront

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_