[BUG]
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When ToolSearch loads a deferred MCP tool's schema, long tool descriptions are truncated with … [truncated] appended. This means Claude never sees the full tool description and may lack critical information needed to use the tool correctly.
Actual Behavior
The description is cut off mid-content with … [truncated]. In the observed case, a tool description containing a Standard Import JSON format specification was truncated in the middle of a JSON example — losing the format details needed to construct valid input for the tool.
Additional Context
- The full description is available when inspecting the tool via the /mcp command — so the MCP server provides the complete description. The truncation happens within ToolSearch itself.
- This is particularly impactful for tools with complex input formats where the description serves as API documentation.
- Since ToolSearch is the only way Claude sees deferred tool descriptions, any truncation directly impacts Claude's ability to use the tool correctly.
What Should Happen?
The full tool description should be returned by ToolSearch, since this is the only mechanism Claude has to learn how to use deferred tools.
Error Messages/Logs
Steps to Reproduce
- Configure an MCP server with a tool that has a long description (e.g.,
one that includes detailed JSON format specifications) (descriptions appear to be truncated after 2048 characters)
- The tool appears in the deferred tools list in the system reminder
- When Claude calls ToolSearch to fetch the tool's full schema, the
returned description is truncated
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.87 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗