blender_render_screenshot

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose the key behavior—capturing the current viewport to an image—but it does not mention output format, resolution behavior, or whether the file is overwritten. For a non-destructive capture operation, this is minimally adequate but not rich.

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, unambiguous sentence with no redundant wording. It front-loads the core action and output without trailing filler or repetition of the tool name.

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?

Given the tool's low complexity, one required parameter, and 100% parameter coverage, the description is mostly complete for an agent to invoke it correctly. Some details like file format or return value are absent, but the essential information needed to call the tool is present.

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 100%, and the output_path parameter is documented as 'Output file path'. The tool description adds no additional meaning beyond the parameter name and schema description, which matches the baseline for full schema coverage.

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 uses a specific verb, 'Capture', identifies the exact resource ('the current viewport'), and states the output form ('as an image'). This clearly distinguishes it from tools like blender_render_image or blender_render_animation, which imply full renders rather than a viewport screenshot.

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 'current viewport' implies when to use this tool: when a quick capture of the visible viewport is needed. However, it does not explicitly contrast this with blender_render_image or mention when not to use it, so the usage context is implied rather than stated.

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