blender_vision_refine

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

With no annotations, the description carries full burden. It discloses the key operations (capture PNG+base64, review multi-angle bundle, apply script) and the refinement cycle. However, it lacks details on error handling, permissions, or return value format, leaving some behavioral aspects uncovered.

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 short and uses bullet points to list operations, making it easy to scan. The key purpose is front-loaded. However, the term 'Agent vision refinement loop' may be jargon, and the structure could be slightly more straightforward.

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 9 parameters with 0% schema description coverage and an output schema (content unknown), the description does not adequately explain the parameters. It only covers operations partially. The description is not complete for this complex 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 coverage is 0% (no descriptions for 9 parameters). The description only loosely references 'operation' and 'output_path' but does not explain parameters like goal, script, resolution_x, resolution_y, include_multi_angle, angles, or output_dir. It adds minimal meaning beyond the schema.

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 is an 'Agent vision refinement loop' and lists three specific operations (capture, review_bundle, apply_script). It distinguishes itself from siblings by focusing on vision-based iterative refinement. However, the title is null, which slightly reduces clarity.

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 this tool is for iterative vision refinement, but it does not explicitly state when to use it versus alternatives like blender_ai_generate or intelligent_3d_processing. No when-not-to-use guidance or alternative tool names are provided.

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