Feature: Dynamically load MCP tool definitions to reduce initial context usage

Problem

When starting a Claude Code session, all MCP tool definitions are loaded into the system prompt upfront, even if they're not immediately needed. This significantly increases initial context usage, making even simple interactions like a single message consume a large amount of the context window.

Requested Solution

Implement lazy-loading or dynamic loading of MCP tool definitions so that:

• Only essential tools are loaded initially
• Additional tools are loaded on-demand when needed
• This reduces the upfront context cost while maintaining full functionality

Impact

This would improve token efficiency, especially for users with limited context budgets or those running many short sessions.