execute_blender_code

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only says code is executed in Blender and recommends step-by-step execution; it does not disclose potential side effects, scene mutation, undo behavior, error handling, or that arbitrary code can be destructive. This is a significant transparency gap for an arbitrary-code-execution 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?

The description is brief and front-loaded with the core purpose in the first sentence. The parameter list is concise and contains no filler, though the step-by-step advice could arguably be moved elsewhere without losing information.

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 an arbitrary code execution tool with no annotations and no output schema, this description is critically incomplete. It omits execution environment details, return format, failure modes, safety warnings, undo implications, and guidance on how this tool integrates with the rest of the Blender workflow. The minimal text leaves the agent without enough context to safely or effectively invoke the 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 description coverage is 0%, so the description must compensate for missing parameter meaning. It restates 'code' as 'The Python code to execute' and adds that 'user_prompt' is 'for telemetry,' but it does not explain execution context, available Blender modules, expected return values, or how the telemetry parameter affects behavior. The added value over the raw schema is minimal.

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 states a specific verb ('Execute') and resource ('arbitrary Python code in Blender'), making the tool's function immediately clear. It is distinct from all sibling tools, which are specialized for asset retrieval, scene inspection, or generation.

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 only usage guidance is 'Make sure to do it step-by-step by breaking it into smaller chunks,' which is a how-to instruction rather than a when-to-use statement. There is no mention of when to prefer this tool over sibling tools or which operations are better handled by specialized tools.

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