go_to_symbol

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

Description mentions it uses workspace symbol search and does not require file location. No annotations provided. Does not disclose error behavior (e.g., symbol not found) or side effects like cursor movement. Adequate but incomplete.

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 concise sentences, no waste. Front-loads key purpose and usage context.

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?

Missing output schema and no annotations. Does not describe return value, error handling, or whether navigation changes document/cursor. Incomplete for a tool with three 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 has 0% description coverage. Description explains symbol_path format (dot-notation) but does not clarify workspace_root or language parameters. Insufficient compensation for missing 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?

Description clearly states the tool navigates to a symbol definition using dot-notation name. It distinguishes from siblings by emphasizing no need for file_path/line/column and uses workspace symbol search.

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?

Explicitly says 'useful when you know the symbol name but not its location', implying when to use. However, does not explicitly name alternative tools like go_to_definition for file-based navigation.

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