move_active_window

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

The description only states the basic operation. It does not disclose effects like boundary behavior, coordinate system, or whether movement is instant. With no annotations, the agent lacks critical behavioral context.

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 sentence with no redundancy. It is front-loaded and concise, but could be slightly more informative without losing brevity.

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 no output schema and simple parameters, the description lacks completeness: no mention of return values, side effects, or prerequisites (e.g., window manager state). Context from sibling tools does not compensate.

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 coverage is 0%, but the description mentions 'pixel delta' and 'absolute position' to hint at parameter semantics. However, it fails to explain the coordinate system (screen vs workspace), units, or the meaning of x and y in both modes.

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' and the resource 'active window', and distinguishes two modes: relative delta and absolute position. This differentiates it from sibling tools like resize_active_window or focus_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?

No guidance is provided on when to use relative vs exact mode, or when to prefer this tool over alternatives like move_window_to_workspace. The description leaves the agent to infer usage context.

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