rhino_lock_selected

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

With no annotations, the description must carry the behavioral burden; it clearly states that locked objects 'cannot be selected or modified.' However, it omits details such as whether lock state persists across documents, whether objects remain visible, and how to reverse the action, so it is adequate but not rich.

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?

A single 13-word sentence states the action, target, and consequence with no filler. It is efficiently front-loaded and appropriate for a zero-argument command.

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 zero-parameter command with an output schema, the description is nearly complete: it identifies the affected objects and the outcome. It could add an unlock alternative or note about no selection, but such gaps are minor for this simple operation.

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 has zero parameters, so the baseline is 4. The description usefully identifies that the target is the current selection, which is the relevant implicit input and requires no parameter documentation.

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 names a specific verb (Lock), a resource (currently selected objects), and the resulting state (cannot be selected or modified). This clearly distinguishes it from sibling tools like rhino_unlock_all or rhino_hide_selected.

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 phrase 'currently selected objects' implies that the command depends on an existing selection, but the description does not state when to prefer this over alternatives such as rhino_unlock_all or rhino_layer_lock. Usage context 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.