rhino_unlock_all

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

No annotations are provided, so the description carries the full disclosure burden. It names the operation and scope but omits edge cases and consequences, such as whether objects locked via locked layers are affected, whether undo covers the action, or whether any confirmation/output is produced. The mutating nature is only implied by the verb 'unlock.'

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, front-loaded sentence with zero filler. Every word earns its place, and the core semantics are immediately visible.

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-argument command with an output schema present, the description pins down the exact state transition (all locked objects become unlocked) and the scope (document-wide). The only missing context is when to use it, which is already penalized under usage_guidelines.

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 with 100% coverage, so the baseline is 4. There is nothing for the description to add about arguments, and it correctly does not invent any.

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 precise verb ('unlock') with an explicit resource and scope ('all locked objects in the document'). This clearly differentiates it from siblings like rhino_lock_selected (locks a selection) and rhino_layer_lock (locks a 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 gives no guidance on when to choose this tool over related siblings such as rhino_lock_selected, rhino_layer_lock, or rhino_show_selected. An agent receives no hint about the typical workflow, such as 'unlock everything before batch editing' or 'use this instead of unlocking objects individually.'

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