blender_render

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

With no annotations, the description should disclose behavioral traits. It only mentions that screenshot_viewport prefers a live GUI session. No info on destructive actions, performance impact, or file overwriting behavior.

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 structured with a list and rationale, but the portmanteau pattern rationale upfront adds unnecessary length. Could be more focused on essential guidance.

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?

With 23 parameters and multiple sub-operations, the description lacks details on how parameters map to operations. Without output schema context, it's insufficient for an agent to correctly invoke the tool.

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%. The description does not explain any parameters; e.g., frames, angles, elevation_deg are not described. The list of sub-operations does not compensate for missing parameter documentation.

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 it consolidates rendering operations, and lists distinct sub-operations (render_preview, render_animation, etc.), which differentiates it from sibling tools like blender_export or blender_compositor.

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 lists many operations but provides no guidance on when to use each sub-operation or alternatives. No explicit context for selection, e.g., when to use render_animation vs render_turntable.

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