ui_hide_window

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

The description conveys the basic mutation (closing a window), but lacks detail on behavior when the window is already closed, error handling, or side effects. Without annotations, more behavioral context would be helpful.

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 one short sentence with no extraneous information. It is optimally concise for a simple 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 tool's simplicity (one parameter, single action), the description is minimally adequate. However, it could include a list of window names or note that closing a hidden window may have no effect. The lack of parameter description reduces completeness.

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 does not explain the 'name' parameter or list the possible window values. With 0% schema description coverage, this is a significant gap. The agent must rely solely on the enum list in the schema, which is not self-explanatory for all values.

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 ('Close') and the resource ('a main window'). It distinguishes from sibling tools like ui_show_window and ui_focused_window, which serve different purposes.

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?

No guidance on when to use this tool versus alternatives. For instance, it doesn't mention that ui_show_window is for opening windows or that ui_focused_window provides window info. Context of use is missing.

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