rhino_sel_none

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Deselect all objects' accurately describes the full behavioral contract: it clears the current selection with no other side effects implied. It does not discuss undo or empty-selection behavior, but these are not significant gaps for such a trivial operation.

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?

Three words with no filler. Every word is necessary and the description is front-loaded with the key information. It could not be more concise while remaining clear.

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, single-purpose tool with an output schema present, the description is fully self-contained. It states both the operation and the complete scope ('all objects'), leaving nothing essential unexplained.

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 100% schema coverage, so the schema already communicates all input information. This is the baseline-4 case for parameterless tools; no additional parameter description is needed.

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 uses the specific verb 'Deselect' with the resource 'all objects', making the operation unambiguous. It is easily distinguished from sibling selection tools such as rhino_sel_all, rhino_sel_invert, and rhino_object_select because none of them express the inverse operation of clearing the selection.

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 directly states its use case: clear the selection of all objects. It does not name alternatives, but for a zero-parameter selection-clearing command, the context is clear and there are no exclusions or prerequisites to document.

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