reveal_in_explorer

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

The description plainly states what the tool does and there are no annotations to contradict. However, with no annotations present, the description carries the full burden and still omits behavioral context such as whether revealing the file also focuses the explorer, whether it opens the file, or what happens when the path is invalid or nonexistent.

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, direct sentence with no filler or redundant wording. It front-loads the verb and clearly identifies the target resource, making it appropriately concise for a one-parameter tool.

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?

For a simple tool with one parameter and no output schema, this description is nearly sufficient on its own. However, the presence of closely related sibling tools creates a real completeness gap: the description does not clarify how 'reveal in explorer' differs from 'select in explorer' or 'focus explorer,' which an agent would need to choose and invoke the right tool reliably.

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 description coverage is 100% for the single 'path' parameter, and the schema already explains it as 'Path to the file to reveal.' The description adds no additional parameter semantics beyond that, so the baseline of 3 is appropriate.

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 states a specific verb, 'Reveal,' and a clear resource, 'a file in VSCode file explorer.' It is not a tautology and communicates the core operation. However, it does not distinguish itself from the closely related sibling tool 'select_file_in_explorer,' which likely performs a similar or overlapping action.

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 about when to use this tool versus siblings such as open_file, focus_explorer, or select_file_in_explorer. There are no exclusions, prerequisites, or alternative conditions stated, so the agent must infer usage entirely from the name and one-line description.

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