viewport_screenshot

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

No annotations are provided, and the description does not disclose any side effects, return behavior, or whether it modifies the scene. It only mentions the GUI requirement, leaving the tool's behavior largely opaque.

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 extremely concise (one sentence), but it omits essential context such as what the output looks like or any operational notes. While brevity is good, the lack of structure or front-loaded key details makes it under-informative.

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 wide range of sibling rendering and capture tools, this description does not provide enough context. It fails to explain output format, return value, when to prefer it over render_image, or any dependencies other than the GUI. The tool's role is not fully defined.

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 provides no descriptions for the parameters, and the description adds nothing about them. The parameter names 'output_path' and 'return_image' hint at their purpose, but without explicit explanation or format details, the semantics are insufficient.

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 action (capture) and the specific resource (3D viewport), and it implicitly distinguishes itself from render_image and render_animation by focusing on the viewport. However, it lacks an explicit contrast with sibling tools.

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 only guidance is the requirement for Blender GUI. There is no instruction on when to use this tool versus alternatives like render_image, nor any mention of typical use cases or limitations.

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