blender_execute_script

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

With no annotations, the description carries the full behavioral burden. It does disclose the execution environment ('bpy' runtime) and the captured outputs (stdout, stderr, a variable named 'result'), which is genuinely useful. However, it says nothing about the safety profile of arbitrary code execution — whether scene changes are irreversible, whether the script can crash Blender, timeouts, or whether errors raise versus return.

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?

Three compact sentences with no filler, and the core action is front-loaded ahead of the use-case list. The final 'Ideal for...' sentence is somewhat generic but still earns its place as routing 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?

An output schema exists, so return values need not be explained, and the single required parameter is simple. The description covers purpose, environment, and capture behavior; the remaining gap is the absence of any warning about the destructive potential of arbitrary script execution.

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% and the single 'script' parameter has no schema description, so the description must compensate. It partially does by defining the execution context (bpy) and the 'result' capture convention, which shapes how the script string should be written, but it adds no format, size, or content constraints.

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 names a specific verb and resource: executing an arbitrary Python script in Blender's 'bpy' runtime. The listed use cases (procedural modeling, rigging, custom automation) implicitly separate it from the narrow siblings like blender_create_object, though no sibling is named explicitly.

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?

'Ideal for procedural modeling, complex operations, rigging, or custom automation' gives a usage context, but these categories overlap with dedicated siblings such as blender_create_object and blender_manage_modifiers. It never states when to prefer this escape hatch over a structured tool, nor any exclusion.

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