render_viewport_to_path

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

The readOnlyHint annotation lowers the bar, and the description does add that the operation targets an output path using current render settings. However, it does not disclose that rendering likely writes or overwrites a file on disk or that rendering can be slow—behavioral traits beyond the annotation, though not directly contradicting it.

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?

A single, front-loaded sentence with no filler. Every phrase ('current scene', 'output_path', 'current render settings') carries operational meaning.

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 one-parameter tool with an output schema and readOnlyHint, the description covers the core operation, but it omits practical details an agent needs: which path or file extensions are valid, whether the file is overwritten, and when to use the sibling render_thumbnail_to_path instead.

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%, so the description must compensate. It places 'output_path' in context as the render destination, but it adds no details about file format, absolute vs relative path, directory existence, or overwrite behavior. The parameter name is self-descriptive enough to avoid a lower score.

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 states a specific action ('Render'), the object ('the current scene'), the destination ('*output_path*'), and the mode ('using current render settings'). This clearly distinguishes it from render_thumbnail_to_path and the screenshot tools, despite the slight viewport/scene wording variance.

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?

There is no guidance about when to prefer this over render_thumbnail_to_path, screenshots, or the execute_blender_code variants. The only contextual hint is 'using current render settings', which implies a full render rather than a thumbnail, but no exclusion or alternative is explicitly named.

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