hide_window

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

Annotations already indicate idempotent and non-destructive behavior. The description adds context on how hiding works (via hwnd/title, minimize option) and the return format, providing additional behavioral insight beyond annotations.

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 sentences efficiently cover purpose, usage example, parameters, and return format. No filler, front-loaded with key information.

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, output schema, and sibling tools, the description provides sufficient context: purpose, parameter overview, return format. It could mention prerequisites (e.g., window must exist) but omission is minor.

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 mentions the window can be identified by hwnd or title and includes a minimize flag, but does not mention the display parameter. Schema descriptions for parameters are present and detailed, but the tool description covers only part of the parameters. With schema description coverage at 0%, the description should compensate more fully.

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: 'Hide a window again after it was shown', using a specific verb and resource. This distinguishes it from sibling tools like 'show_window' and 'hide_headless_desktop'.

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 implies usage after showing a window (e.g., after login), but does not explicitly state when not to use it or compare to alternatives. No exclusion criteria or guidance on choosing between hiding vs minimizing vs closing.

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