rhino_set_display_mode

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

There are no annotations, so the description carries the behavioral disclosure burden. It does state that the active viewport's display mode is changed and enumerates the legal modes, which is reasonable for a simple viewport setter. However, it does not mention persistence, whether geometry is unaffected, or how invalid mode values are handled.

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 compact and front-loaded, stating the primary purpose in the first sentence and then providing the necessary parameter values in a clear list. There is no redundant filler or repetition of schema field titles.

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 one-parameter setter with an output schema, the description covers the essential information: what is affected, the valid mode choices, and the active-viewport scope. It is sufficiently complete for straightforward invocation, though it could benefit from a note distinguishing it from similar display-mode tools.

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 schema only declares a string mode with a default value and no enum, so the description adds significant value by listing the exact accepted values: Wireframe, Shaded, Rendered, Ghosted, Raytraced, ArtisticRendering, Pen, and Technical. It does not explain each mode's visual meaning, but the names are largely self-explanatory.

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 clearly states the action: set the active viewport display mode, with a specific resource and a specific list of accepted values. However, it does not differentiate this tool from the sibling rhino_display_mode_set, which appears to have the same or very similar purpose.

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?

No guidance is provided about when to use this tool versus alternatives such as rhino_display_mode_set, rhino_set_view, or rhino_viewport_preview. The description does not mention preconditions, when this setting is appropriate, or when another tool should be chosen instead.

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