Bring folder window to front

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

No annotations are provided, so the description carries the burden. It discloses that the tool targets an open window and un-minimizes if needed, and the hwnd parameter description reveals that ambiguous matches produce a list of hwnds for retry. This is adequate for a simple, non-destructive focus action.

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 main description is one focused sentence with no filler. The schema's hwnd explanation is longer but purposeful, providing necessary retry guidance without unnecessary verbosity.

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 definition covers the required path, optional hwnd disambiguation, and what happens when multiple windows match. It does not explicitly state behavior when no matching window exists or describe return values, but these are minor gaps for a simple focus action with no output schema.

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%, so the baseline is 3. The path and hwnd parameters are already well documented in the schema, including friendly names and retry behavior. The main description adds no additional parameter-level meaning.

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 clear verb and resource: 'Show and switch focus to an open File Explorer window for the given folder (un-minimizes if needed).' It distinguishes itself from siblings like open_path and minimize_folder_window by emphasizing an existing window and un-minimizing behavior.

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?

The description clearly implies this is for already-open File Explorer windows, and the hwnd guidance provides a concrete workflow for ambiguous cases. However, it does not explicitly name alternatives or state when not to use this tool versus open_path or focus_app.

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