ui_minimize_window

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

Annotations only include openWorldHint: false, which is minimally informative. The description adds that it uses WindowPattern (UIA), indicating it interacts with native UI. However, it does not disclose behavior in edge cases (e.g., window not found), whether it supports non-top-level windows, or system permissions required.

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 two sentences with no wasted words. It front-loads the primary action and then briefly explains the parameter. This structure is efficient for an agent to quickly understand the 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?

Given the simple nature of the tool and the set of siblings, the description is fairly complete but lacks details on error handling, return behavior, and explicit differentiation from related tools like ui_close_window or ui_restore_window. For an agent to handle all scenarios, more context on failure modes would be beneficial.

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 0%, so the description must compensate. It does so effectively by explaining that 'window_title' is an optional partial title match and omitting targets the main window. This adds meaning beyond the schema's type and default, though it could clarify matching rules (e.g., case sensitivity).

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: 'Minimize a top-level window via WindowPattern.' It uses a specific verb and resource, and the tool name aligns with this. Among siblings like ui_maximize_window, ui_restore_window, ui_close_window, this tool's purpose is distinct.

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 provides guidance on the optional 'window_title' parameter: 'Optional partial title match. Omit to target main window.' This clarifies when to provide a title vs not, but it does not explicitly state when to use this tool over alternatives (e.g., minimizing vs closing a window) or mention any prerequisites.

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