execute_blender_code

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

With no annotations, the description carries the full burden. It clearly states that the tool executes arbitrary Blender Python code and explains the file_path behavior. However, it does not disclose whether scene changes persist, what the return value might be (e.g., stdout, errors), or any safety caveats, leaving notable gaps for an agent.

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 compact and well-structured: a one-sentence purpose, two sentences of usage guidance, and a three-bullet parameter list. Every sentence adds value and nothing is redundant.

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 complex code-execution tool with no output schema, the description covers parameters and usage well. However, it does not mention what the tool returns after execution, whether errors are surfaced, or if changes to the Blender scene persist. This is a meaningful gap given the tool's power and the absence of structured output information.

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 provides only raw string fields with no descriptions, and coverage is 0%. The description fully compensates with a clean parameter list that explains code, file_path, and user_prompt, including the optional relationship and precedence. This is far beyond what the schema supplies.

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' with a specific verb and resource. It is unmistakably distinct from sibling tools, which are all getters or asset-management operations, and no other tool executes arbitrary code.

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?

It gives practical guidance on passing code vs. file_path, including the trade-off (server reads file, cheaper for large scripts) and precedence when both are provided. It does not explicitly list alternatives or exclusions, but the sibling tools are clearly different in purpose, so the guidance is sufficient.

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