rhino_ungroup

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It communicates that this is a mutating operation and that individual objects are released from the group. It does not discuss edge cases or selection prerequisites, but the core behavior is transparent.

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 no filler. Every phrase contributes meaning: the action, the target, and the result.

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 operation, the description sufficiently conveys the action, target, and expected outcome. It leaves the selection mechanism implicit, but the phrase 'selected groups' is enough to guide correct invocation in the Rhino context.

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 input schema has zero properties and full coverage, so there are no parameters for the description to clarify. The phrase 'selected groups' correctly refers to Rhino's document selection state rather than a formal argument, which the empty schema makes clear.

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?

States a specific verb ('Ungroup') and resource ('selected groups'), and clarifies the outcome ('releasing individual objects'). This distinguishes it from related operations like rhino_group, rhino_explode, or rhino_block_explode.

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 implies the context of use: groups must be selected in the Rhino document. It does not explicitly name exclusions or alternatives, but for a zero-parameter selection-based tool this provides adequate guidance.

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