pro_visualize_render_project

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

Annotations only declare it is a non-read-only, non-destructive, non-idempotent, closed-world call; the description adds meaningful context beyond that: a prerequisite (installed Offline Renderer), the side-effect scope ('on a new copy', 'Source projects remain unchanged'), and the async lifecycle with request_id. It does not describe failure modes or what happens if the renderer is missing, but the added behavioral value is substantial.

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?

Four short sentences, each carrying distinct information: what it does, optional camera/scene adjustments, side-effect scope, and async handling. Front-loaded with the action and free of 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?

For a 12-parameter mutation tool with no output schema, the description covers the async contract and non-destructiveness well but omits what the call returns and the meaning of most render-quality parameters. It is adequate to invoke the tool but not to invoke it well.

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 all twelve parameters rely on the description for meaning. It explains reference_project_path ('pin its active camera to a reference project'), ground_shadows/ground_reflections, and the request_id reuse rule, but leaves width, height, passes, denoiser, camera_position_mm, camera_target_mm, and vertical_fov_deg completely unexplained in both schema and description.

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 verb and resource ('Render a native Visualize project') plus the engine used ('installed Offline Renderer'), and adds the scope that output goes to a new copy. It is clear on its own, but it never explicitly separates itself from the similarly named sibling pro_visualize_render, so an agent must infer the distinction from the words 'native Visualize project'.

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 real operational guidance for the async pattern ('Poll pro_operation; do not repeat a running request_id'), which tells the agent what to do after calling. However, it offers no explicit when-to-use/when-not guidance versus pro_visualize_render, pro_visualize_status, or pro_render_job, so alternative selection is left implied.

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