blender_render_viewport

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

With no annotations provided, the description carries the full burden. It usefully discloses the side effect (writes a PNG to disk) and the response content (file path and resolution), but says nothing about overwrite behavior, required auth/context, or whether the full render blocks or is long-running.

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?

Two tight sentences with the primary action front-loaded and no filler. Slightly terse given the unstructured parameters, but nothing is wasted.

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?

An output schema exists, so return-value explanation is not strictly needed, and the description still summarizes the return. However, with zero annotation coverage and zero schema description coverage, the absence of any output_path or default-behavior explanation leaves real gaps for a tool that writes files.

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 0%, so both parameters are undocumented in structured data. The description obliquely conveys what full_render does via the two render modes, but never names the parameter, and output_path is entirely unexplained (no default-path or format guidance), so it fails to compensate for the coverage gap.

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 names a specific verb and resource ('Captures a viewport preview screenshot ... or triggers a full Cycles/EEVEE render'), clearly distinguishing the two modes. No sibling tool in the list performs rendering, so differentiation is implicit 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?

It contrasts 'fast OpenGL render' with 'full Cycles/EEVEE render', which implies when each mode is appropriate, but it never explicitly says which mode to choose or when to avoid one. No prerequisite or exclusion guidance is given, leaving the selection to inference.

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