lsp_get_capabilities

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

No annotations provided. Description adds that initialization is optional (startIfNeeded), but does not explain side effects of initialization, what 'normalized' means, or what response to expect. Minimal behavioral disclosure for a tool with no annotations.

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?

Single sentence that is concise and front-loaded. Every word contributes to the purpose. No wasted text.

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?

Given no output schema and many sibling tools, description is incomplete. Does not explain what 'normalized LSP capabilities' include, when to use this vs lsp_get_config or lsp_health_check, or how to interpret the result. Lacks depth.

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%, so baseline is 3. Description does not add meaning beyond what the schema provides (language and startIfNeeded). No extra detail on valid values or format.

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?

Description clearly states it returns normalized LSP capabilities and optionally initializes the server. It is specific about the resource (LSP capabilities) but does not explicitly distinguish from siblings like lsp_get_config or lsp_server_status. Many sibling tools exist, but the purpose is clear enough.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, exclusions, or context for when to set startIfNeeded. Agent must infer usage from the description and param names.

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