move_window

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

The description discloses the key behavior of passing -1 to keep a parameter's current value, which is helpful. However, no annotations exist, and the description doesn't mention potential limitations or side effects, such as whether the window is brought to foreground or if it works on minimized windows.

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 compact and well-structured, with a brief summary followed by a parameter list. No unnecessary wording.

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 window manipulation tool, the description covers the essential parameters and the -1 behavior. It omits details like coordinate reference (screen vs client) and error behavior, but the output schema likely covers return values. The description is mostly complete for standard use.

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?

Every parameter in the schema is explained in the description with units and the -1 sentinel meaning. This fully compensates for the 0% schema description coverage.

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 tool's function: 'Move and/or resize a window.' It uses a specific verb and resource, and distinguishes from sibling resize_window by covering both move and resize operations.

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 this tool versus alternatives like resize_window or set_window_state. The description only explains what the tool does and its parameters, without mentioning exclusions or prerequisites.

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