show_window

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds context about bringing to foreground and human interaction, but does not detail what happens if the window is already visible (though implied by idempotentHint). No contradictions.

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 brief paragraphs plus an Args/Returns section, every sentence adds value. No redundancy or 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?

Given the tool's simplicity, annotations, and schema, the description covers the key aspects: purpose, usage context, parameters, and return format. It does not mention error cases or edge conditions, but these are not critical for this 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?

The description says 'the window by hwnd or title,' which summarizes the parameters succinctly. The input schema already contains detailed descriptions for each parameter (hwnd, display, window_title), so the description adds only marginal value beyond that.

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: 'Make a hidden/minimized window visible and bring it to the foreground.' It distinguishes from sibling hide_window and provides a concrete use case (login).

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 describes when to use this tool ('when an automated app on the normal desktop hits a step that needs the human - typically an interactive LOGIN') and points to the alternative hide_window to resume automation afterward.

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