capture_scene_render

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

Beyond annotations (which indicate non-read-only and non-destructive), the description reveals important runtime behavior: it runs with -force-d3d11 (not -nographics) to avoid black images, and instructs to open output_png after job completion. This adds value but could detail job failure handling or permissions.

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 concise (3 sentences) and front-loads the main action. Each sentence serves a purpose, but the second and third sentences could be integrated for better flow without losing clarity.

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 lacks explanation of the job mechanism, return value (likely job ID), and how to retrieve the final PNG. With no output schema, this leaves significant gaps for an agent to correctly invoke and use the tool's result.

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%, yet the description only mentions output_png in context. It does not explain parameters like project_path, scene_path, width, height, or version, leaving the agent without sufficient guidance for parameter values.

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 the tool renders a camera of a scene headless into a PNG for visual inspection. It specifies the output format and that the image can be used for error detection. However, it does not explicitly differentiate from sibling tools like blender_render_preview.

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 the tool is for visual inspection but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The usage context is implied but not thorough.

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