blender_render_extras

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

Annotations indicate readOnlyHint=false, meaning the tool likely has side effects (e.g., modifying scene, saving files), but the description does not disclose any such side effects. It only mentions the clay preview uses Workbench and is near-instant, which is a performance detail but does not clarify the non-read-only nature or potential modifications to scene/render settings.

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 (two sentences) but is not well-structured. It lists actions in a prose list without front-loading the most critical information (e.g., that the tool is action-driven). It is not verbose, but it also does not use bullet points or emphasize the action parameter.

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?

The tool has 11 parameters, 4 actions, and no output schema, yet the description does not explain how actions map to parameters or what the expected return format is. It also fails to mention that it is a multi-action dispatcher or how to choose an action. This is inadequate for an agent to call it correctly without deeper schema inspection.

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 already provides descriptions for many parameters (e.g., pivot, frames, images, passes, output_dir), and the description adds no additional parameter semantics. With 73% schema coverage, the description could have filled gaps (e.g., what 'cell', 'columns', 'resolution' mean in context), but it does not.

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 lists four distinct actions (turntable renders, clay preview, render pass toggles, contact sheets) which clearly states what the tool does. However, it does not differentiate from sibling tools like blender_render or blender_capture_viewport, leaving the agent uncertain about when to choose this over those.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention exclusions or prerequisites, nor does it explain which action to pick for a given scenario. The agent is left to infer usage from the schema alone.

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