rhino_render_preview

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Start a quick preview render.' It does not disclose whether this renders to the active viewport, blocks until complete, requires render setup, or has any side effects. The behavioral trait 'quick preview' is helpful but not sufficient given the lack of annotations.

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 five-word sentence with no filler and the main verb is front-loaded. For a zero-parameter tool, this is appropriately sized and easily scannable.

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?

The tool is simple with no parameters and an output schema exists, so the description does not need to explain return values. However, it lacks behavioral context and tool-selection guidance, and given the large family of rendering and preview tools, an agent may not have enough context to invoke it confidently.

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 takes zero parameters and the schema coverage is 100%, so the schema fully accounts for the argument surface. Per baseline guidance for zero-parameter tools, the description need not add parameter details, and it does not need to compensate for any schema gap.

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 states a specific verb ('Start') and a resource ('quick preview render'), so the core action is clear. However, it does not differentiate from close siblings like rhino_render_viewport or rhino_viewport_preview, leaving some ambiguity about exactly which preview rendering workflow is invoked.

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?

There is no guidance about when to use this tool instead of alternatives such as rhino_render_to_file, rhino_render_viewport, or rhino_viewport_preview. The phrase 'quick preview' implies a lightweight render, but no explicit when-to-use or exclusion criteria are provided.

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