rhino_delete_selected

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It says the tool deletes selected objects, which is informative, but it does not mention that deletion is destructive, whether it is undoable, what happens if nothing is selected, or any side effects on the current selection state.

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, direct sentence contains the full essential meaning with no filler. It is front-loaded with the action and the object scope, making it easy for an agent to parse quickly.

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 tool with no parameters and a simple operation, the description is largely complete. The main gap is the lack of behavioral caveats around destructive changes and empty selection behavior, but the core invocation context is clear.

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 schema coverage is 100%, so a baseline of 4 applies. The description usefully clarifies that the implicit input is the current selection, which is the only meaningful semantic context 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 a specific verb ('Delete') and a precisely scoped resource ('currently selected objects'), which clearly differentiates it from sibling tools like rhino_object_delete. The phrase 'currently selected' is a meaningful qualifier that tells an agent exactly what this tool operates on.

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 provides clear context: this tool is appropriate when the user wants to delete the objects currently selected in the Rhino document. It does not explicitly name alternatives or when-not-to-use conditions, so it falls short of a 5, but the usage context is unambiguous.

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