blender_render

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

Annotations already indicate readOnlyHint=false, so the agent knows mutations are possible. The description adds a little context, such as 'screenshot_viewport: ... prefers live GUI session', but does not disclose side effects like changing Blender settings or writing files beyond the operation names. It does not contradict the annotations.

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 well-structured with a bullet list and example, making it easy to scan. The inclusion of 'PORTMANTEAU PATTERN RATIONALE' is unnecessary meta-commentary, but the rest is informative and front-loaded with the core purpose.

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 23 parameters with no schema descriptions, the description is not fully complete. It lists operations but does not map which parameters are relevant for each operation, nor does it clarify the distinction between output_path and output_dir. The presence of an output schema helps with return values, but the parameter mapping gap remains.

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?

With 0% schema coverage, the description must compensate. It partially does by explaining operations that map to parameters (e.g., 'set_engine' covers render_engine/samples/device, 'setup_post_processing' covers bloom/SSAO/motion blur/DOF). However, many parameters like output_dir, frame_start, resolution, and elevation_deg are left undefined, so the compensation is incomplete.

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 into a single interface' and lists concrete sub-operations like render_preview, render_turntable, and render_animation. This makes it unmistakably the rendering-focused tool, distinguishing it from siblings like blender_animation or blender_scene.

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 via the operation list (e.g., use 'render_preview' for a single frame), and the example shows a typical call. However, it never explicitly says when to prefer this tool over alternatives or when not to use it, leaving the agent to infer the context.

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