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 discloses that the tool executes arbitrary code, which implies potential side effects, but it does not warn about dangers, failure modes, or effects on Blender scenes. The step-by-step hint is a recommendation rather than a description of tool behavior, leaving significant transparency gaps.

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 two sentences, front-loaded with the core purpose, and includes a brief, practical tip. There is no fluff or repetition, making it appropriately concise and well-structured.

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?

The tool has an output schema, so return values need no explanation. The description covers the core action and provides a step-by-step safety tip, which is useful. However, given the complexity of arbitrary code execution, more context such as Blender environment details (e.g., pre-imported modules, potential timeouts) would make it more complete, so it settles at an adequate but not comprehensive level.

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 add meaning. It says 'code: The Python code to execute', which simply restates the parameter name and suggests no additional details about format, execution environment, or restrictions. This adds minimal value beyond the schema's title, failing to compensate for the lack of schema descriptions.

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 'Execute arbitrary Python code in Blender', which uses a specific verb ('execute'), identifies the resource ('Blender'), and conveys that this tool runs any Python code. It distinguishes itself from sibling tools by being the only one that directly executes custom code, making its purpose unambiguous.

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 gives clear context: it is for running arbitrary Python code in Blender, implying use when other specific tools are insufficient. It also provides a directive to break execution into smaller chunks, which serves as a practical usage guideline. However, it does not explicitly mention when not to use it or name alternative tools, so it slightly misses the top score.

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