restart_lsp_server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions optional reinitialization with a new root directory and clarifies that the server won't auto-initialize if root_dir is omitted. However, it does not disclose side effects like loss of unsaved state, impact on open documents, or required permissions, which are important for a restart operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, with the core action in the first sentence. It is succinct, front-loaded, and contains no filler or redundant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool without an output schema, the description covers the main purpose, common use cases, and parameter behavior. Minor gaps exist (e.g., side effects), but overall it provides enough context for an AI agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (root_dir is fully described in the schema). The description adds minor context by explaining that root_dir is optional and controls reinitialization, but it doesn't significantly go beyond the schema's own explanation. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Restart the LSP server process,' which clearly states the specific action and resource. It distinguishes this tool from siblings like start_lsp (initial startup) and get_diagnostics (inspection) by focusing on restarting an existing server.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists when to use the tool: 'if it becomes unresponsive, has stale data, or when you need to apply configuration changes' and 'when switching projects.' It provides clear context but does not explicitly mention alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.