archicad_move_elements

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, which establishes the mutation-but-not-destructive profile. The description adds real value beyond that by naming the recovery path ('Revert with archicad_undo'), telling the agent the move is an undoable operation rather than an irreversible one.

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 the operation and its addressing scope front-loaded, followed immediately by the recovery instruction. No filler; every clause carries information.

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 5-parameter mutation tool with no output schema, the description covers what moves, how it is addressed, the unit, and the undo path. It stops short of describing return content or whether dryRun counts as touching the model, though the schema's dryRun description partially covers that.

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 80%, so the baseline is 3, and the description earns the bump by supplying the unit ('by a vector in meters') that the schema omits for x/y/z, plus confirming that the three addressing modes map onto the elements/selectedOnly/elementType parameters.

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 (moves) plus resource (elements) and explicitly enumerates the three addressing modes: explicit list, selection, or a type. This distinguishes it from rotate/delete siblings, though it does not name the near-identical MoveElements sibling it sits next to.

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 by listing the three element-selection modes and points to archicad_undo as the revert path, which is genuinely helpful. It never states when to prefer one selection mode over another, nor any prerequisite (e.g. model must be open, selection must be active), so guidance is implied rather than explicit.

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