go_to_definition

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

No annotations provided, so description carries full burden. Discloses zero-based coordinate system (critical behavioral detail), specifies output format (file path, line, column), and implies no side effects. No contradictions.

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?

Concise description at 5 sentences, well-structured with USAGE and OUTPUT sections, and an IMPORTANT note. No extraneous words, front-loaded with the primary purpose.

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, the description fully covers purpose, usage instructions, prerequisites, behavioral nuances (zero-based), and return format. Complete for a navigation tool with simple parameters.

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%, but description adds value by explaining zero-based coordinates and that filePath can be absolute or relative, enhancing meaning beyond schema descriptions.

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 the tool navigates to a symbol definition, specifies the action (navigate) and resource (symbol definition), and differentiates from sibling tools like find_references and find_implementations by focusing on the definition location.

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 usage direction: position cursor on symbol reference, returns definition location. Explicitly states prerequisite 'Requires load_project to be called first.' Could be improved by explicitly stating when not to use (e.g., for references), but guidance is effective.

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