minimize_current_window

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

The description adds context (whole-window operation, no elementId needed) beyond the idempotentHint annotation, but does not disclose any side effects, return value, or state changes. The annotation already indicates safe repeated calls, but behavioral details are minimal.

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?

Single sentence, front-loaded with the action and resource, and includes a parenthetical clarification. Every word serves a purpose with no redundancy.

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 (no parameters, no output schema, idempotent annotation), the description is adequate. It explains the key distinction from minimize_window, which is the most important context. Could briefly mention that the window is minimized to the taskbar or how to restore, but not essential.

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?

With zero parameters, the description does not need to explain them, but it adds value by clarifying why no elementId is required, contrasting with a sibling tool. This provides semantic context beyond the empty schema.

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?

Clearly states the verb 'minimize' and the resource 'current session's root window'. Explicitly distinguishes from sibling 'minimize_window' by noting it does not require an elementId, making the purpose unambiguous.

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?

Provides a direct comparison with 'minimize_window' by highlighting the lack of elementId requirement, which helps the agent choose between them. However, it does not elaborate on when to use the tool versus other window operations or general context.

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