{"version":"2.1.318","anchor":"toolsearch-can-leave-out-tool-definitions-that-dont-fit-the","canonical_anchor":"toolsearch-can-leave-out-tool-definitions-that-dont-fit-the","heading":"Tool search can skip tool definitions that don't fit the remaining room","tier":"notice","area":"Tool Search","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/toolsearch-can-leave-out-tool-definitions-that-dont-fit-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Tool search can skip tool definitions that don't fit the remaining room\n\nTool search can leave out matched tools that are already loaded or too large for the remaining space, and tell Claude why\n\n**What**\n\nTool search is how Claude finds and loads tools that are held back until needed. After a search, Claude Code can now measure the size of each matched tool's definition and leave some out:\n\n- tools that are already loaded\n\n- tools too large for the context window on their own (the context window is the amount of text Claude can hold at once)\n\n- tools that would go over the room still left\n\nWhen tools are left out, Claude receives a note saying why. This size check is off unless it is switched on remotely with a fraction of the context to use.\n\n**Why**\n\nIt stops a search from pulling in very large tool definitions, such as big MCP tool descriptions, that would overflow what Claude can hold.\n\n- Flag `tengu_measured_shelf`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Tool Search\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}