move_elements_by

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

Describes the operation (shift by dx/dy) and parameter directions, but does not disclose return value details, side effects, or whether the action is reversible. With no annotations, the description carries full burden and falls short on behavioral completeness.

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?

Very concise, front-loaded with purpose, followed by structured argument explanation. Every sentence adds value without redundancy. No filler.

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?

Given the tool's simplicity and the presence of an output schema (not shown), the description covers input parameters well. Lacks mention of limitations (e.g., invalid IDs, connected elements) but is otherwise adequate for a straightforward move operation.

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 description compensates fully with a clear argument block explaining each parameter's meaning, units, and direction (positive = right/down). Adds significant value beyond the schema's bare type and title information.

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?

Clearly states the tool shifts elements by a relative offset. Distinguishes from siblings like 'set_positions' (absolute) and 'find_elements' (search) by noting it avoids needing to query coordinates first.

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?

Explicitly gives usage context: use when user says 'move generator 200px right' without needing coordinates. Also provides guidance to call 'find_elements' first for pattern moves. Covers prerequisites and typical use cases.

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