rhino_render_setup

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

readOnlyHint=false already signals mutation, and the description's 'Set' is consistent with that. It adds the useful detail that the operation targets the active render context, but it does not explain persistence, whether settings are replaced wholesale, or whether a subsequent render action is needed.

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 front-loaded sentence with no filler. The slash-separated list of settings and the target 'active render context' convey the tool's purpose efficiently.

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?

Adequate for a simple setter but not fully complete: it leaves out the output_path setting and does not place the tool in the render workflow relative to sibling render tools. An agent can probably invoke it correctly from the schema, but the workflow context and one parameter are missing from the description.

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 description maps well to several schema fields by grouping width/height as 'resolution' and naming samples, engine, and transparency. However, it omits output_path entirely, and with schema description coverage reported at 0%, the description does not sufficiently compensate for the lack of parameter-level documentation.

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 identifies the tool as a setter for render resolution, samples, engine, and transparency on the active render context. The verb and resource are specific, though it does not explicitly distinguish itself from sibling tools like rhino_set_render_resolution or rhino_render_viewport.

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 related tools such as rhino_render_to_file, rhino_render_preview, or rhino_render_viewport. The description says what the tool does but not how it fits into a render workflow or when it should be invoked.

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