{"version":"2.1.293","anchor":"tool-not-found-errors-tailored-for-the-agent-tool-and-disabl","canonical_anchor":"tool-not-found-errors-tailored-for-the-agent-tool-and-disabl","heading":"Clearer guidance for Claude when it asks for a tool it cannot use","tier":"notice","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/tool-not-found-errors-tailored-for-the-agent-tool-and-disabl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Clearer guidance for Claude when it asks for a tool it cannot use\n\nWhen Claude calls a tool that is not available, the error now says whether it is disabled or simply not offered here, with special advice for `Agent`\n\n**What**\n\nWhen Claude tries to use a tool it does not have, Claude Code sends back an error. That error used to say every time that the tool was disabled for the session, in subagents too. It now tells two cases apart:\n\n- The tool is disabled for this session.\n\n- The tool is not among the tools available here, and Claude should continue with the ones it has.\n\nFor the `Agent` tool, which starts subagents (helper copies of Claude that work on a side task), it also says \"An agent cannot be continued from this context.\" and tells Claude to start a new call instead.\n\n**Why**\n\nClaude gets more accurate advice on how to recover after a bad tool call, so it is less likely to keep retrying something that cannot work.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}