cinematic_render

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

No annotations are provided, so the description must carry the full burden. It describes the rendering features and presets but does not disclose any side effects (e.g., file creation, overwriting), permission requirements, performance considerations, or limitations. This lack of behavioral context, especially for a tool with many parameters, leaves the agent guessing.

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 front-loaded with key features followed by a bullet list of effects and a numbered list of quality presets. It is well-structured and reasonably concise, though the bullet list could be slightly tighter.

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 19 parameters, no output schema, and no annotations, the description covers the overall purpose and quality presets well. However, it lacks explanation of output format (just 'PNG'), how auto-camera and parameter interactions work, and typical use cases. It is adequate but not comprehensive.

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?

The input schema has 100% parameter description coverage, so the description's role is diminished. The description adds value by explaining auto-camera and lighting features in context, but it does not significantly enhance understanding beyond what the schema already provides for individual parameters.

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 it's for cinematic-quality rendering with auto-framing, 3-point lighting, SSAO, and PBR, distinguishing it from simpler tools like render or preview_3d. The list of effects and quality presets makes the purpose unmistakable.

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 this tool is for high-quality, publication-ready images, and the quality presets give context for when to use each. However, it does not explicitly state when to prefer this over sibling tools like render or batch_render, which slightly reduces clarity.

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