turntable

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

With no annotations, the description carries the full burden. It discloses that every frame is ray-traced and slow, that the ray_trace option is ignored, and that the unshaded OpenGL renderer silently produced blank frames in this environment. This is thorough and honest about limitations.

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?

Three concise paragraphs: purpose, method, and performance/alternative. Each sentence earns its place, with no redundancy. The most important information is front-loaded.

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 7 parameters, full schema coverage, an output schema, and no annotations, the description is remarkably complete. It covers the output format, performance characteristics, and known issues, leaving no critical gaps for an agent to invoke the tool 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?

Schema description coverage is 100%, so baseline is 3. The description adds some context (e.g., prefix pattern and ffmpeg usage) but does not significantly enhance per-parameter meaning beyond what the schema already provides. The schema descriptions are already detailed, so the description's added value here is limited.

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 opens with a specific verb+resource: 'Renders a full 360° rotation as a numbered PNG sequence.' It clearly distinguishes itself from sibling tools like 'turn' or 'rock' by focusing on producing a frame sequence for GIF/MP4 assembly.

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?

Explicitly states when to use: to create a rotation sequence for GIF/MP4. Provides an alternative (OpenGL renderer) and why it's not used (does not work over the bridge), plus performance guidance to start with few frames and small dimensions. This is clear usage context.

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