render_camera_to_png

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

The description discloses synchronous rendering, force behavior, and headless operation. It lacks details on side effects like file overwriting, permissions, or error handling. No annotations are present, so the description carries the full burden.

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?

Two sentences, no wasted words. Key information is front-loaded: verb, resource, output format, and special capability (headless).

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?

No output schema is provided, but the description does not mention what is returned (e.g., success/failure, file path). It covers the main behavioral aspects but lacks return-value information, which is important for an agent to handle the tool's response.

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 coverage is 100% with parameter descriptions. The description adds context by explaining that width/height/camera_label trigger off-screen capture and that fov overrides the current FOV. This goes beyond the schema's individual descriptions.

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 the level-editor viewport or an off-screen SceneCapture2D to a PNG file. It distinguishes itself from sibling tools like 'get_viewport_screenshot' by noting it works headless/backgrounded where deferred screenshots fail.

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 when to use this tool (headless/backgrounded) and when off-screen capture is triggered (width/height/camera_label). However, it does not explicitly mention alternatives or when not to use it.

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