rhino_move_objects_to_layer

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

No annotations are provided, so the description carries the full behavioral disclosure burden. The description only says 'Move', which implies mutation, but it does not clarify whether the target layer must already exist, whether the layer is created automatically, what happens with no selection, or whether the operation 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?

The description is short, front-loaded with the main action, and includes a clean Args section. Every word earns its place, and there is no unnecessary 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?

The tool is simple and has an output schema, but behavioral context is missing: what happens if the layer does not exist, whether object selection is a hard prerequisite, and how errors are reported are not addressed. This is noticeable for a mutating tool with no annotations.

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 schema provides no description for layer_name, and the description adds only 'Target layer name.' This is a minimal clarification that essentially restates the parameter name, but because it is a single, self-explanatory string parameter, the basic semantic guidance is adequate.

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 states the exact action ('Move currently selected objects') and the destination ('to the specified layer'). The phrase 'currently selected' clearly distinguishes this from tools that take explicit object IDs, such as rhino_object_move_to_layer.

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 clearly establishes when the tool should be used: when objects are currently selected and need to be moved to a specified layer. It does not explicitly name alternatives or say 'use this instead of X', but the precondition is unambiguous.

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