ui_move_window

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

The description discloses that the tool returns a structured error object when the window cannot be moved (CanMove=false) and that it does not raise an exception. This adds behavioral context beyond the annotations, which only include openWorldHint=false. It does not detail side effects or permissions, but is sufficient.

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 concise: a brief sentence for the action, a clear line about the return format, and a structured Args section. Every sentence adds value without repetition.

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 tool with 3 parameters and no output schema, the description covers the action, return value on failure, and parameter semantics completely. It provides enough context for effective selection and invocation.

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 explicitly defines all three parameters: x and y as target screen coordinates, and window_title as optional with a hint to omit for main window. Since schema description coverage is 0%, this adds critical meaning beyond type/title.

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 ('Move a window to screen coordinates (x, y)') and the resource ('window'), with specification of the underlying pattern (TransformPattern). It is specific and distinguishes from sibling tools like ui_resize_window or ui_maximize_window.

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 context on when it returns the error object and emphasizes that no exception is raised. However, it does not explicitly state when to use this tool vs alternatives (e.g., ui_switch_window) or note when not to use it.

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