go_to_implementation

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

No annotations present; description does not disclose prerequisites, error conditions, or side effects. It mentions using LSP and returning paths and positions, but lacks details on required state or limitations.

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?

Three concise sentences with no redundancy. Front-loads the purpose and then provides usage guidance. Every sentence adds value.

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 annotations, no output schema, and partial parameter coverage, the description is incomplete. Lacks details on parameter formats, return structure, error handling, and prerequisites. Sibling tool differentiation could be stronger.

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 has 0% parameter description coverage; description adds meaning for file_path, line, column by implying they specify the location, but ignores language_id entirely. Does not compensate for the lack of schema details.

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 the tool finds implementations of interfaces or abstract methods, uses specific verbs and resources, and implicitly distinguishes from siblings like go_to_definition by specifying the use case of navigating to concrete implementations.

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?

Provides clear context on when to use: navigating from interface declaration or abstract method to concrete classes. Does not explicitly mention alternatives or when not to use, but the guidance is sufficient.

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