rhino_layer_purge_unused

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 discloses that this is a destructive operation and precisely specifies what will be deleted: layers with no objects and no sub-layers. This is meaningful transparency beyond the empty schema, though it does not mention undo behavior or locked-layer edge cases.

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 then defines the exact filtering condition. Every part of the sentence contributes necessary information.

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 parameterless destructive tool with an output schema available, the description is largely complete: it defines the action, the target scope, and the filter. Minor gaps include lack of explicit warning about irreversibility and no mention of the current-document scope, but these do not seriously impair agent decision-making.

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 tool has zero parameters and the schema is empty, so there is no parameter documentation burden. The description adds value by defining the implicit scope of the operation ('all layers' matching the deletion criteria), which is the only semantic information an agent needs.

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 specific verb ('Delete'), a specific resource ('all layers'), and precise selection criteria ('contain no objects and have no sub-layers'). This clearly distinguishes it from related tools like rhino_layer_delete, which deletes a named layer, and rhino_purge, which is a broader purge command.

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 use this tool versus alternatives such as rhino_layer_delete or rhino_purge. There are no stated prerequisites, exclusions, or context about when a cleanup of unused layers is appropriate.

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