rhino_turntable

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

Annotations indicate readOnlyHint: false, which is consistent with the description's 'render' implying a write operation. No contradictions, but the description does not add significant behavioral context beyond what annotations imply (e.g., does not mention side effects, prerequisites, 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 with no extraneous words. Front-loads the core purpose and output format. Very efficient.

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 description lacks context about required model state (e.g., a 3D object to animate), view settings, and how to choose between PNG sequence vs GIF. While an output schema exists, the description omits crucial setup details for a rendering tool.

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 the output_path parameter. Other parameters (width, height, frames, doc_id) have no additional explanation, leaving the agent to infer their meaning from schema constraints alone.

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) and resource (turntable animation) with output to a specific path in PNG or GIF format. It uniquely identifies the tool among siblings performing other render operations.

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 explicit guidance on when to use this tool versus alternatives like rhino_turntable_render or rhino_render_to_file. The description only implies usage for turntable animations without providing context or exclusions.

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