femm_move_selected

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses defaults (origin for 'about', FEMM's current edit mode for entities) and rotation direction (counter-clockwise), but says nothing about reversibility/undo, mutation side effects, or the session parameter's role.

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 dense sentences that are front-loaded with the core operation and then qualify it. Every clause carries information (mode, direction, pivot, entity scope, default), with 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 6-parameter mutation tool with no annotations and no output schema, the description covers most semantics adequately but omits the 'session' parameter and any mutation/undo behavior. It is minimally sufficient but has clear gaps.

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 must compensate, and it does well: it defines dx/dy as translation, rotate_deg as counter-clockwise degrees, about as an [x, y] pivot defaulting to origin, and enumerates entities values. Only 'session' is left unexplained.

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 the selection') with its two concrete modes (translate by dx/dy, rotate by rotate_deg). An agent can immediately understand the operation, though it does not explicitly distinguish itself from transform siblings like femm_mirror_selected or femm_scale_selected beyond the verb itself.

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?

Gives conditional guidance for the entities filter ('use "group" after femm_select(kind="group")') and a default behavior, which is useful. However, it offers no when-to-use/when-not framing relative to the other selection-transform tools, leaving the agent to infer.

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