move_objects

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

With no annotations, the description must carry the full burden. 'Wait until all have settled' usefully discloses that the call is blocking/synchronous, but it doesn't cover permissions, whether motion is animated by default (smooth=true), failure behavior if a guid is invalid, or whether the move is undoable.

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?

Front-loaded action sentence followed by a tight two-branch list; every sentence earns its place. The trailing newline/formatting is slightly rough but not confusing.

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?

A 4-parameter, zero-coverage, annotation-free mutation tool needs more: the `smooth` flag, mutual exclusivity of the two modes, and what 'settled' means operationally are all unaddressed, and there is no output schema to fall back on.

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%, so the description is the only documentation. It does add real meaning for `moves` (guid/position/rotation keys) and `offset` (dx,dy,dz formation-preserving shift), but leaves `smooth` completely undocumented and doesn't state precedence between `moves` and `guids`+`offset`.

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?

States a specific verb ('move') and resource ('several objects at once') plus a behavioral promise ('wait until all have settled'). It implicitly distinguishes itself from the singular sibling move_object via 'several', but never names the alternative explicitly.

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?

Clear routing between two invocation modes: explicit per-object targets via `moves`, or a shared `offset` applied to `guids` to preserve formation. No guidance on when to prefer this over calling move_object repeatedly, and no statement on what happens if both modes are supplied.

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