execute_blender_code

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention potential side effects, irreversibility, error handling, or the fact that code runs in Blender's context and can mutate scenes—critical information for a tool that executes arbitrary code.

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 exceptionally concise, with the main purpose in a single sentence and one useful procedural note. It is front-loaded and contains no extraneous 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 a tool that executes arbitrary code, the description is insufficient. It omits return values, output behavior, error handling, and side effects, and there is no output schema or annotations to fill these gaps. The procedural note is helpful but does not make the description complete.

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 description defines the 'code' parameter as 'The Python code to execute,' which adds minimal meaning beyond the schema's title 'Code.' It does not clarify expected format, length, or execution constraints, but it does at least explain the parameter's purpose.

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 'Execute arbitrary Python code in Blender,' which is a specific verb+resource combination that clearly differentiates it from sibling tools focused on asset generation, status checks, and scene information.

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 instruction to 'do it step-by-step by breaking it into smaller chunks' provides procedural guidance but does not explicitly state when to use this tool versus alternatives or when not to use it. The use case is implied rather than clearly articulated.

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