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 full burden. It clearly indicates a restart/reset behavior and optional reinitialization, but does not disclose potential side effects like losing document state or requiring reconfiguration. The description implies a reset but lacks explicit detail about consequences.

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 concise, front-loaded with the action 'Restart the LSP server process,' and uses three sentences to convey purpose, when to use, and optional behavior. Every sentence adds value without redundancy.

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 tool with one optional parameter and no output schema, the description adequately covers purpose, triggers, and the optional root directory behavior. It even provides context for troubleshooting and project switching, making it reasonably complete.

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 description coverage is 100%, as the parameter 'root_dir' has a clear description. The tool description adds 'Can optionally reinitialize with a new root directory,' which slightly reinforces the schema but does not add significant new semantics beyond what the schema already provides.

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 clearly states 'Restart the LSP server process' with a specific verb and resource. It distinguishes itself from sibling tools like start_lsp by focusing on restarting an existing process, and mentions use cases like unresponsiveness and stale data.

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?

Explicitly states when to use: 'if it becomes unresponsive, has stale data, or when you need to apply configuration changes' and 'when switching projects.' It also notes the option to reinitialize with a new root directory, 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.