rhino_sel_layer

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

With no annotations provided, the description carries the full burden of explaining behavior. It only says 'Select all objects on a specific layer' and gives no detail on whether the current selection is replaced, whether the layer name must already exist, or whether selection is additive.

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 a single, front-loaded sentence with no wasted words. It immediately states the action and the target, which is appropriate for a simple one-parameter selection tool.

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 minimal selection tool with one parameter, the description is minimally viable. However, because there are no annotations and no explanation of selection side effects or layer-name expectations, the context is not fully complete despite the presence of an output schema.

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 description coverage is 0%, so the description must compensate for documenting layer_name. It only says 'on a specific layer,' which confirms the parameter identifies a layer but does not clarify matching behavior, exact-name requirements, or case sensitivity.

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 a clear action ('Select all objects') and the resource/criterion ('on a specific layer'). It is easy to distinguish from layer-management tools like rhino_layer_list or object-movement tools like rhino_object_move_to_layer, though it does not explicitly name alternatives.

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?

There is no guidance about when to use this tool versus related selection or layer tools such as rhino_sel_by_name, rhino_layer_isolate, or rhino_object_move_to_layer. The intended context is implied but not stated.

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