Skip to content
← Back to release · 2.1.293
New features / v2.1.293

isDeferred option for mod tool registration

CHANGELOG · original

Added isDeferred to $.tool.register for mods: false lists the tool's schema in the prompt from the start instead of behind tool search
Open official changelog ↗

Documentation

Documentation excerpt

Tools

Tool events fire around each tool call Claude makes, from the description Claude reads to the decision on whether the call runs:

Event Fires when A hook can return
tool.call A tool is about to run next(e), { deny: reason }, or { result }
tool.check Claude Code decides whether a tool call may run, after the tool.call and PreToolUse hooks. next(e) resolves to the decision the rules, the permission mode, and those hooks reached. next(e) or { decision }, with decision set to allow, ask, or deny and an optional reason
tool.describe Once for each tool, when its description is first sent to Claude. A second time for an MCP tool when Claude loads it through tool search, with e.description set to the text Claude reads for the loaded tool. { description }, optionally with isDeferred set to true to put the tool behind tool search or false to load it upfront. Add breakPromptCache: true to send a changed description on the next turn.

Agent and organization fields on tool.check

In a tool.check hook, read these fields to tell a subagent's call from the main conversation's, and to see whether your organization requires approval for a connector tool:

On tool.check, e.agentId and e.ceiling require Claude Code v2.1.290 or later.

The e.isReadOnly field on tool.check

In a tool.check hook, e.isReadOnly is true when the tool reports this call as read-only. Otherwise the field is absent, not false. The value is the tool's own report, so read Check whether a tool call is read-only before you approve a call on this field alone.

On tool.check, e.isReadOnly requires Claude Code v2.1.304 or later.

Documentation snapshot · 2026-11-20

Change details