[DOCS] Missing LSP tool in primary reference and agent system instructions

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings#tools-available-to-claude

Section/Topic

The "Tools available to Claude" reference table in the public documentation and the corresponding tool definitions within the Agent System Prompt.

Current Documentation

The public table lists 17 tools (from AskUserQuestion to Write).
The internal system prompt (v2.1.12) used by the agent also lacks an entry for the LSP tool under its # Tools section, listing the same standard toolkit.

What's Wrong or Missing?

While the LSP Servers documentation and the v2.0.74 Changelog confirm the existence of an LSP tool for code intelligence (diagnostics, find-references, go-to-definition), the tool is entirely missing from:

1. The primary public reference table: Making it difficult for users to know if the tool requires manual permission configuration.
2. The Agent's internal system prompt: Even in version 2.1.12, the agent is not "explicitly" taught about an LSP tool in its core definitions, suggesting it is only treated as a dynamic capability provided via the plugin system.

This omission creates a "feature-gap" where users expect LSP capabilities (like real-time diagnostics sharing), but the primary documentation does not define the tool's parameters, timeouts, or permission requirements.

Suggested Improvement

Add a row to the "Tools available to Claude" table in settings.md:

| Tool | Description | Permission Required |
| :--- | :--- | :--- |
| LSP | Provides real-time code intelligence, including go-to-definition, find-references, and diagnostic sharing via Language Server Protocol. | No |

Additionally, ensure the internal agent definitions are updated so the model understands the LSP tool's scope alongside Read and Grep.

Impact

High - Prevents users from using a feature

Additional Context

• System Prompt Analysis: Analysis of the v2.1.12 (2026-01-17) hidden system prompt confirms that while tools like Bash, Grep, and TodoWrite have explicit schemas provided to the model, the LSP tool is absent.
• Inconsistency: The documentation encourages users to install LSP plugins (e.g., pyright-lsp, rust-lsp), yet the core tool used by those plugins is never defined in the master tool list.
• Permission Clarity: Since diagnostics sharing happens automatically after edits (as per v2.0.74), defining this as a "No Permission Required" tool in the public docs will reduce user confusion regarding background activity.