render_turntable

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose the return behavior ('Returns an animated image (APNG) inline'), which is meaningful. However, it does not mention rendering time, potential side effects, failure modes, or whether the input code is modified or just read, leaving some behavioral ambiguity.

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 extremely concise: two sentences with no filler. It front-loads the core purpose in the first sentence and adds the key output detail in the second. Every word earns its place.

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?

For a tool with no output schema and no annotations, the description gives the essential purpose and return type but leaves gaps. The nested 'params' object is completely unexplained, which could be important for passing OpenSCAD variables. Still, the core calling pattern is clear: provide OpenSCAD code and get turntable APNG, so it is minimally viable.

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 coverage is 80%, so the baseline is 3. The description adds no additional parameter meaning beyond the schema. It does reinforce that 'frames' relates to a 360° turntable animation, but this is a minor enhancement over the schema's own 'Number of frames (default 24)' description.

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 a specific action ('Render a 360° turntable animation of the model') and identifies the exact output ('animated image APNG inline'). This distinguishes it from sibling tools like render or render_multiview because it uniquely specifies the turntable animation format, so an agent can select it correctly without opening the schema.

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 implies usage: when you need a 360° turntable animation, this is the tool. It also mentions the inline APNG return, which hints at how the output will be consumed. However, it does not explicitly contrast with sibling tools like render or render_multiview, nor does it state when not to use it.

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