{"version":"2.1.323","anchor":"remotetrigger-and-comments-tools-get-whentouse-and-registry","canonical_anchor":"remotetrigger-and-comments-tools-get-whentouse-and-registry","heading":"Several tools now tell Claude when to use them","tier":"notice","area":"Tool Hints","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remotetrigger-and-comments-tools-get-whentouse-and-registry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Several tools now tell Claude when to use them\n\nRoutines, web fetch, web search, AskUserQuestion and other tools now carry guidance on when Claude should reach for them\n\n**What**\n\nSeveral of Claude Code's tools, the actions Claude can take, now carry a short note telling the model when to use them:\n\n- The routines tool: prefer it over the local scheduler when a job must run on a schedule or event while Claude Code is closed.\n\n- `WebFetch`: use it to read a public web page; it cannot reach most private or signed-in pages, or localhost.\n\n- `WebSearch`: use it instead of memory alone for something recent or past the model's knowledge cutoff.\n\n- `AskUserQuestion`: use it instead of a plain-text question when stopping to wait for your answer.\n\n- The goal-proposal tool: not for one-off tasks.\n\nThese tools, along with the artifact comments tool and a few others, also gain a fixed identifier. The main descriptions of `WebFetch`, `WebSearch` and `AskUserQuestion` are unchanged in the capture taken under this release.\n\n**Why**\n\nThe notes steer Claude toward the right tool, such as choosing a routine instead of a local timer for a job that has to run while Claude Code is closed.\n\n- Area: Tool Hints\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}