goto_definition

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

With no annotations, the description must describe all behavioral traits. It only says 'go to definition' without explaining side effects (e.g., whether it opens a file, returns a location, or highlights). The agent cannot predict the tool's full behavior.

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?

The description is a single sentence that is front-loaded and contains no wasted words. However, it could be slightly expanded to include behavioral hints without losing 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 no output schema, the description should clarify what the tool returns or does (e.g., open location, return range). It lacks this information, making it incomplete for an AI agent to understand the call's outcome.

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 the parameters 'file', 'line', and 'col' are already fully described. The description adds no additional meaning beyond 'at a given position', which is already implied by the schema.

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 action ('Go to definition') and the resource ('symbol at a given position via LSP'). It effectively distinguishes from siblings like 'get_references' or 'goto_implementation' by specifying the exact navigation target.

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 this tool versus alternatives such as 'get_references' or 'hover'. The agent receives no context about prerequisites, typical use cases, or exclusions.

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