minimize_main_window

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

With no annotations, the description carries the full burden, and it discloses nothing beyond the action name: no idempotency, reversibility, required connection state, or what happens to the session. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single tight sentence that is front-loaded and free of waste. It is arguably under-specified rather than overwritten, but structurally it is fine.

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?

For a simple one-parameter window action the description is minimally sufficient, but it omits the only parameter's meaning and any behavioral context, leaving the agent to rely entirely on the name and schema.

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 single required parameter sessionId has 0% schema description coverage, and the description never mentions it or explains which session's window is affected. The schema's uuid format hints at the type but adds no semantic meaning 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?

States a specific verb+resource ('Minimize Electron main window'), which is unambiguous and distinct from the sibling cluster of maximize_main_window, focus_main_window, and get_main_window_info. It does not, however, explicitly route the agent away from those siblings.

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 versus focus_main_window or maximize_main_window, nor any stated precondition (e.g., window must exist, session must be connected). The agent must infer usage from the name alone.

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