claude-code - 💡(How to fix) Fix [DOCS] Tools reference missing Advisor Tool documentation [1 participants]

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/tools-reference

Section/Topic

Built-in tools reference / experimental tool coverage

Current Documentation

The docs currently say:

Claude Code has access to a set of built-in tools that help it understand and modify your codebase. The tool names are the exact strings you use in permission rules, subagent tool lists, and hook matchers.

To add custom tools, connect an MCP server. To extend Claude with reusable prompt-based workflows, write a skill, which runs through the existing Skill tool rather than adding a new tool entry.

| Agent | Spawns a subagent with its own context window to handle a task | | AskUserQuestion | Asks multiple-choice questions to gather requirements or clarify ambiguity | | Bash | Executes shell commands in your environment | ... | ToolSearch | Searches for and loads deferred tools when tool search is enabled | | WebFetch | Fetches content from a specified URL | | WebSearch | Performs web searches | | Write | Creates or overwrites files |

No documentation currently exists for an Advisor or Advisor Tool entry in the Claude Code docs.

What's Wrong or Missing?

Changelog v2.1.117 describes a user-visible Advisor Tool (experimental) feature: the dialog now shows an experimental label, a learn-more link, and a startup notification when enabled, and the release also fixes repeated Advisor tool result content could not be processed failures on every prompt and /compact.

The docs do not explain:

A. What the Advisor Tool is

There is no built-in tool reference entry or feature overview for Advisor Tool.

B. How users enable or recognize it

The changelog implies an enablement path plus visible UI states (experimental label, learn-more link, startup notification), but none of that is documented.

C. What its current limitations are

Because this is explicitly labeled experimental, users need a short description of availability, limitations, and troubleshooting expectations.

Suggested Improvement

Add an Advisor Tool (experimental) entry to the built-in tools documentation, or add a dedicated page linked from tools-reference, covering:

1. What the Advisor Tool does and when Claude Code uses it
2. How to enable it, including any required setting, flag, account restriction, or rollout condition
3. What users should expect in the UI (experimental label, learn-more link, startup notification)
4. Current limitations and any known caveats for this experimental feature
5. Basic troubleshooting guidance for Advisor Tool result-processing failures

If enablement is controlled through settings or feature flags, add a cross-reference from the relevant settings page as well.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 1 page affected

Source: Changelog v2.1.117

Exact changelog entry:

Advisor Tool (experimental): dialog now carries an "experimental" label, learn-more link, and startup notification when enabled; sessions no longer get stuck with "Advisor tool result content could not be processed" errors on every prompt and /compact