capture_render_snapshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the tool requests a snapshot, but it does not disclose whether the call is blocking or asynchronous, whether it is read-only, whether a render must be actively running, or what the caller can expect in the response.

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 a single, front-loaded sentence with no filler. It introduces the action, the output type, and the scope without repeating schema information.

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?

With no output schema and no annotations, the description should explain the return behavior and preconditions, but it leaves these implicit. The distinction from interactive-viewer snapshot tools is only implied through the phrase 'native-host render,' and no guidance is given about valid job states or failure cases.

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 schema has a single required parameter, job_id, with 0% description coverage, and the description does not explain what job_id refers to or where the caller should obtain it. 'Native-host render' gives some context, but it does not compensate for the lack of parameter documentation.

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 states a specific action ('Request'), a specific resource ('current-frame EXR and PNG preview'), and a specific context ('native-host render'). This clearly differentiates it from the sibling capture_interactive_viewer_snapshot, which targets an interactive viewer.

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 phrase 'native-host render' provides a useful context cue that this tool is meant for render jobs rather than interactive viewer sessions, but it does not explicitly state when to use this tool over alternatives like capture_interactive_viewer_snapshot or render_preview, nor does it mention any exclusions or prerequisites.

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