lsp_incoming_calls

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

No annotations, but description implies read-only operation. Mentions 'cached' data and maps to standard LSP method. Does not disclose details like sync/async, error conditions, or side effects. Sufficient for a simple query tool.

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?

Two sentences, no waste. First sentence delivers core purpose and mechanism, second sentence maps to LSP. Efficient and front-loaded.

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?

No output schema, but LSP call hierarchy return format is standard. Description covers purpose, parameters, and prerequisite. For an LSP-savvy agent, it's mostly complete. Could mention return type briefly.

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% with descriptions. Description adds 'using a cached call hierarchy item ID', clarifying itemId's origin and purpose beyond schema's 'opaque item ID'. For maxResults, schema already provides meaning. Adds moderate value.

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 verb 'find' and resource 'callers of a function or method', specifies mechanism 'using a cached call hierarchy item ID', and maps to LSP method. Distinguishes from siblings like lsp_outgoing_calls and lsp_prepare_call_hierarchy.

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?

Hints at prerequisite (item ID from lsp_prepare_call_hierarchy) but lacks explicit when-to-use vs alternatives like lsp_outgoing_calls or lsp_references. No when-not-to-use guidance. Adequate but not comprehensive.

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