get_viewport_screenshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Capture') and return type ('Image'), but lacks details on permissions, rate limits, or side effects (e.g., whether it pauses Blender operations). It adds basic context but misses key behavioral traits for a capture tool.

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 front-loaded with the core purpose in the first sentence, followed by a clear parameter explanation and return statement. Every sentence adds value without redundancy, and the structure is logical and efficient for a tool with minimal parameters.

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 (1 parameter, no output schema, no annotations), the description is moderately complete. It covers the purpose, parameter, and return type, but lacks output details (e.g., image format, dimensions) and behavioral context like error handling. It meets minimum viability but has gaps in transparency and guidelines.

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 description adds meaningful semantics beyond the input schema, which has 0% coverage. It explains that 'max_size' is the 'Maximum size in pixels for the largest dimension' with a default of 800, clarifying its purpose and units. With only one parameter, this adequately compensates for the schema gap, though it doesn't detail constraints like minimum/maximum 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 specific action ('Capture a screenshot') and target resource ('current Blender 3D viewport'), distinguishing it from siblings like 'render_still' (which renders a full image) or 'get_scene_info' (which retrieves metadata). The verb+resource combination is precise and unambiguous.

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 usage context (when a screenshot of the viewport is needed) but doesn't explicitly state when to use this tool versus alternatives like 'render_still' for higher-quality renders or 'get_scene_info' for non-visual data. No exclusions or prerequisites are mentioned, leaving usage decisions to inference.

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