minimize_window

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

The annotation declares idempotentHint=true, and the description does not contradict this. However, it does not elaborate on what happens to the window (e.g., whether it goes to taskbar, if focus shifts, or if the element becomes invalid). Given the annotation covers idempotency, a score of 3 is appropriate as the description adds minimal behavioral context beyond the annotation.

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 concise sentence that gets straight to the point. It could be slightly improved by front-loading the action more clearly, but it is efficient and contains no filler.

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 has only one parameter, no output schema, and the idempotent annotation, the description is mostly adequate. However, it lacks any mention of return value or side effects (e.g., whether a new window state can be queried). For a simple tool, this is acceptable but not complete.

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 schema already documents the single parameter elementId. The description adds no additional meaning beyond what the schema provides. Baseline 3 is correct when the schema fully covers the parameter.

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 verb 'Minimize' and the resource 'a window element via the UIA Window pattern'. It specifies the action precisely and differentiates from siblings like maximize_window, restore_window, and close_window by naming the specific pattern used.

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?

There is no guidance on when to use this tool versus alternatives such as minimize_current_window or close_window. The description does not explain prerequisites (e.g., element must represent a window), nor does it indicate when this is preferred over other window manipulation tools.

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