move_entity

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

Without annotations, the description carries the burden of behavioral disclosure. It reveals that handle='selection' affects the GUI selection, a useful nuance. But it does not disclose whether the operation is permanent, error handling, coordinate system, or units for dx/dy.

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?

One sentence, front-loaded with the core operation and a special case. No wasted words; every word earns its place.

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 tool has three required parameters and no annotations, so the description must provide enough context for correct invocation. It fails to explain the format of handle for non-selection entities, the coordinate space, and when to use this tool relative to siblings.

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?

The description explains dx and dy as the move offset, which is helpful given 0% schema coverage. It also documents the special 'selection' value for handle. However, it does not explain what other handle values look like or how they identify entities.

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 operation ('Move entity by (dx,dy)') and distinguishes it from siblings like move_all by implying this targets a specific entity. It also explains the special 'selection' handle value, adding clarity.

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 implies usage for moving a specific entity by an offset, and the 'selection' special value provides some guidance. However, it does not explicitly say when to use this over move_all, copy_entity, or other transform tools, nor does it state any prerequisites.

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