Start Photorealistic Render

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

Beyond the annotations, it disloses the asynchronous behavior ('poll get_render_status') and a critical environmental limitation ('Jobs die if Fusion exits'). This is material operational context that an agent could not infer from schema or annotations alone. It does not cover file-writing side effects, but the disclosure is strong.

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 short sentences with the core action front-loaded, followed by the required polling step, a critical caveat, and the preview alternative. Every sentence earns its place and there is no redundant restatement of the title.

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 an asynchronous tool with no output schema, it covers the follow-up action, a key failure mode, and the preview alternative, which is genuinely useful. However, it never states what start_render returns or how the agent links the started job to get_render_status, so part of the invocation contract remains implicit. With eight optional parameters and no output schema, that is a real gap.

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 description adds no parameter-level meaning; it dose not map resolution, fit, transparent_background, or filename to render behavior. Schema description coverage is only 63%, leaving several parameters undocumented in both schema and description. The description dost not compensate for this gap.

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?

States a specific action ('Start a raytraced render') on a clear resource, making its photorealistic purpose explicit. The description also distinguishes it from the sibling render_view by noting that previews belong there. There is no ambiguity about what the tool does.

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?

Gives an explicit workflow: start the render, then poll get_render_status. It names render_view as the alternative for previews, which tells an agent when not to use this tool. This is direct usage routing rather than implied context.

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