lsp_hover

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

With no annotations, the description should disclose behavioral traits. It omits that an active LSP session is required (implied by session_id), does not describe output format or potential empty results, and lacks details on side effects (likely none). The behavior is only vaguely described.

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?

A single, front-loaded sentence contains all essential information with no redundancy. Every word earns its place, achieving maximum conciseness.

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 the output schema exists (covering return values), the description is fairly complete for a simple query tool. However, it could mention that the tool requires a started LSP session (implied by session_id) and that results may be absent for some positions.

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?

All 4 parameters have descriptions in the schema (100% coverage), so the description adds no extra meaning. Baseline 3 is appropriate; the description does not explain parameter purpose beyond what 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 it retrieves 'type and documentation info at a specific code position,' which is a specific verb+resource pair. It distinguishes well from siblings like lsp_goto_definition (jump to definition) and lsp_signature_help (function signature).

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 is provided on when to use lsp_hover versus other LSP tools (e.g., lsp_signature_help for signatures, lsp_goto_definition for navigation). The description does not mention alternatives or conditions.

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