rhino_turntable_render

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

The description indicates a rendering operation and mentions writing to output_dir, but it does not disclose side effects such as file creation, overwriting behavior, render time, or failure modes. The readOnlyHint: false annotation is consistent with the described behavior, so there is no contradiction.

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, focused sentence that directly states the operation and key references. It is concise and front-loaded, with no unnecessary words or redundant information.

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?

Given the complex input schema and numerous parameters, the description is too sparse. It does not explain the meaning or defaults of key parameters like frame count, radius, or sample settings, and it lacks context about expected output or prerequisites, making it incomplete for an agent to use correctly without additional information.

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?

Schema description coverage is 0%, and the description only clarifies target and output_dir, which are already partially named in the schema. Many parameters such as width, height, radius, samples, frame_count, and render_height are left unexplained, so the description does not compensate for the missing schema 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 states the tool renders a turntable sequence with the camera orbiting a target, which distinguishes it from general render or camera tools. However, it does not mention specific output format or additional behavior, so it is clear but not fully differentiating.

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 gives no explicit guidance on when to use this tool versus alternatives like rhino_turntable, rhino_render_to_file, or rhino_render_preview. The implied usage is present but not stated, and no when-not-to-use conditions are provided.

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