rhino_hide_selected

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

With no annotations present, the description carries the burden of disclosing behavior. It clearly states the core action on selected objects, but it does not mention that hiding is reversible, what happens if no objects are selected, or that the objects are not deleted.

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 filler. Every word earns its place.

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 command with an output schema, this is almost complete: the target (currently selected objects) and action (hide) are clear. A note about reversibility or the no-selection case would make it fully complete.

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?

There are zero parameters and the schema is empty, so there is nothing to document. The description still adds valuable context by specifying that the tool operates on the current selection rather than taking explicit arguments.

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 ('Hide') and names the exact resource ('currently selected objects'), making it easy to distinguish from sibling selection tools such as rhino_delete_selected, rhino_lock_selected, and rhino_show_selected.

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 phrase 'currently selected objects' implies the prerequisite of an active selection and the use case of making selected geometry invisible. It does not explicitly state when not to use it or point to alternatives like rhino_show_selected for reversing the action, so guidance is only implied.

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