controlMove

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety/mutation profile is covered. The description adds genuine context beyond annotations by stating the trusted-owner and interactive-desktop environment requirements, but says nothing about what effect the move has or reversibility.

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 short sentences with no filler, but the first sentence is a name restatement that adds no information. It is brief yet under-specified rather than efficiently informative.

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 7-parameter mutation tool with no output schema, the description omits what actually gets moved or resized, how x/y interact with width/height, and any failure behavior. The environment note is helpful but leaves the core operation underspecified.

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 100%, so all seven parameters including the required title, control, x, and y are self-documented. The description adds no meaning beyond the schema (no unit, coordinate-space, or width/height semantics), so the baseline 3 applies.

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?

"Windows AutoIt controlMove" restates the tool name with a platform qualifier rather than stating what it does; an agent must infer the action (move/resize a control) from the name alone. It does not distinguish from siblings like winMove, controlSetText, or controlGetPos.

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 only guidance is the precondition "Requires a trusted owner and an interactive Windows x64 desktop," which is a prerequisite rather than a when-to-use. It never says when to choose this over winMove or other control tools, nor what conditions make it fail.

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