select_file_in_explorer

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the immediate UI effect. It does not disclose whether the explorer gets focused or auto-expanded, whether the action fails for nonexistent paths, or whether editor state is affected.

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?

A single, front-loaded sentence with zero filler. Every word contributes to stating the tool's function.

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?

The tool is simple (one param, no output schema), so the description is nearly adequate. The main gap is unresolved ambiguity with reveal_in_explorer and no disclosure of failure behavior, which matters in a UI-state-changing tool.

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 schema already documents the path parameter's type, requirement, and meaning. The description adds no additional value such as absolute-vs-relative path expectations or whether folders are also selectable.

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 names a specific verb ('select/highlight') and resource ('a file in VSCode file explorer'), making the core operation clear. However, it does not explicitly differentiate from the near-sibling reveal_in_explorer, which overlaps heavily in meaning.

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 given on when to use this tool versus alternatives such as open_file, reveal_in_explorer, or focus_explorer. An agent has no stated basis for choosing this tool over its near-synonym reveal_in_explorer.

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