blender_render

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

With no annotations, the description carries the full burden, and it does disclose real behavioral context: coordinate conventions (az 0 = front/-Y), what ortho does, how focus frames a world-space region, and that it returns images. However it is silent on scene side effects, the timeout, ignore_gpu_guard, engine selection, and error behavior for 10-param 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?

Front-loaded with the core purpose, then dense per-parameter detail with no filler. The inline JSON examples are compact, though the mode cross-reference to blender_turntable defers information an agent may not be able to resolve.

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 10-parameter tool with no annotations and no output schema, the description covers roughly half the parameters and the important geometry conventions. It omits several behavioral params (engine, timeout, ignore_gpu_guard, light, size) and gives only 'Returns the images' as a return-value note, leaving the definition partially complete.

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 the description must compensate. It adds genuine meaning for views (az/el format and orientation), objects, ortho, and focus with a concrete example, but leaves mode, size, light, engine, timeout, and ignore_gpu_guard entirely undocumented in both schema and description.

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?

States a specific verb and resource: 'Render explicit camera views', which clearly distinguishes it from the sibling turntable tool by emphasizing explicit az/el camera control. It does not name blender_render_scene or explain the split, but the resource and mechanism are 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?

Usage is only implied: the tool is for when you want specific framed camera angles rather than an orbit. It references blender_turntable for 'Modes as in' but does not state when to choose this tool over blender_turntable or blender_render_scene.

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