move_window

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

The description adds the key behavioral trait that omitted parameters leave dimensions unchanged. The annotations already indicate destructiveHint=true, so this dimension does not need to repeat that. No contradictions.

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?

Two sentences with no wasted words. All information is front-loaded and essential.

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?

The description covers basic behavior but lacks details about matching (exact vs substring), behavior when no window matches, and potential side effects beyond destructiveness. Given annotations and no output schema, more completeness would be helpful.

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?

With 0% schema description coverage, the description compensates by explaining the effect of omitting x, y, width, height. However, it does not specify coordinate units or matching behavior for title_pattern.

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: moving and/or resizing a window. It uses a specific verb+resource and distinguishes from siblings like close_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?

The description explains that omitted dimensions remain unchanged, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or edge cases like no matching window.

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