rhino_turntable_render

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

Annotations already indicate readOnlyHint=false, so it's known that this tool produces output. The description adds that it generates image files to a directory, but doesn't disclose whether it modifies the Rhino document, side effects, or performance implications.

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?

Single sentence, no fluff. Could be slightly more structured (e.g., listing key parameters) but is appropriate for a tool with a clear primary purpose.

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 complexity (7 parameters, no schema descriptions) and the presence of an output schema (not shown), the description is too sparse. It omits return value, error conditions, and usage context like required model setup, making it hard for an agent to use correctly.

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?

With 0% schema description coverage, the description only mentions 'target' and 'output_dir' in the context, but provides no additional meaning for the other 5 parameters (width, height, radius, samples, frame_count, render_height). The tool relies entirely on parameter names and defaults, which is insufficient for correct invocation.

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 ('Render a turntable sequence') and resource ('camera orbits around target to output_dir'). It distinguishes from sibling render tools by specifying this is for turntable animation, though it doesn't explicitly differentiate from the related 'rhino_turntable' tool.

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 on when to use this tool versus alternatives like standard rendering or other turntable-related commands. No mention of prerequisites, required model state, or comparison to siblings.

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