move_bpmn_element

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

Annotations already declare the mutation (readOnlyHint=false), idempotency, and closed-world scope. The description adds real behavioral context beyond that: resize preserves top-left, laneId auto-centers and ignores x/y, and batch moves are validated up front and collapse into one undo step.

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 sentences, front-loaded with the core action, then the constraint, then the batch alternative. Every clause carries information; 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?

For a mutating tool with annotations covering safety and idempotency and no output schema, the description covers operations, constraints, and batch behavior well. It could note failure modes (e.g., invalid laneId/elementId) but is largely complete.

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 baseline is 3, but the description adds the combination semantics (any mix of coordinates/size/lane, at least one required) that the schema does not express, plus the top-left/auto-center behavior. It earns above baseline without duplicating schema text.

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 specific verbs (move, resize, reassign) plus the resource (BPMN element to a lane), and the sibling set (align_bpmn_elements, layout_bpmn_diagram) is clearly not this operation. An agent can distinguish it without opening the schema.

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?

Explains the constraint that any combination is allowed but at least one of x/y, width/height, or laneId is required, and explicitly routes to the batch `moves` form for several elements. It does not name competing siblings (align/layout), so it falls just short of a 5.

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