Render Active Document

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does disclose that rendering 'may take up to 60 seconds' and that it uses the currently active render data. However, it does not mention whether the call blocks, what it returns, or how it handles existing files at the output path.

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 compact: two sentences, with the core action and scope front-loaded. The prerequisite guidance and timeout note are included without redundancy or filler.

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 covers the primary action, configuration prerequisite, and expected runtime, but no output schema or annotations exist. It does not state the return value or completion behavior after rendering, nor does it guide the agent between this tool and similar siblings like preview_render and rs_render.

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% for the single output_path parameter, so the schema already fully documents it. The tool description adds no additional parameter-specific meaning, matching the baseline for high coverage.

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 identifies a specific verb ('Render') and resource ('active Cinema 4D document') and scopes it to 'currently-active render data settings.' However, it does not explicitly differentiate this tool from sibling render-related tools like preview_render or rs_render, so it stops short of full sibling differentiation.

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 provides helpful context: rendering uses the active RenderData, and users should change settings first via create_render_data or set_params. It does not state when to prefer this tool over alternatives such as preview_render or rs_render, leaving the comparison to inference.

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