get_viewport_screenshot

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the return type ('Returns the screenshot as an Image') and parameter semantics, but does not explicitly note that this is a non-destructive read-only operation or address potential failure modes (e.g., no viewport open).

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 concise and well-structured: a one-sentence purpose, a clear parameter explanation, and a brief return statement. Every sentence earns its place without unnecessary verbosity.

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?

For a simple tool with one parameter, no annotations, and no output schema, the description covers the core aspects: what it does, how the parameter works, and what the return value is. However, it omits potential edge cases or prerequisites (e.g., Blender running with an active viewport), which could be useful.

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 only defines max_size as an integer with a default, but the description explains it as 'Maximum size in pixels for the largest dimension,' adding crucial meaning. Since schema description coverage is 0%, the description fully compensates by documenting the parameter's purpose.

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's function: 'Capture a screenshot of the current Blender 3D viewport.' This is a specific verb+resource pairing that distinguishes it from sibling tools like get_scene_info or get_object_info, which focus on data rather than visuals.

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 provides no explicit guidance on when to use this tool versus alternatives. While it is implied that this is the tool for capturing viewport images, there is no mention of use cases, prerequisites, or exclusions.

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