execute_blender_code_for_cli

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

The description adds meaningful behavior beyond the `destructiveHint: true` annotation: it states that `blend_file` is opened with `blender --background`, that arbitrary Python `code` is run, and that data must be assigned to `result` to be returned. This gives the agent a clear execution model without contradicting the annotation.

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 very short and front-loaded: the core purpose is in the first sentence, followed by the essential invocation and return mechanism. Every sentence earns its place and there is no redundancy.

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?

Given the tool's simple two-parameter shape, the existence of an output schema, and the `destructiveHint` annotation, the description covers the key operational facts: how the file is opened, what code does, and how to return data. The main missing piece is explicit differentiation from the sibling `execute_blender_code`, but this is not critical for invoking the tool correctly.

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?

With 0% schema description coverage, the description must carry parameter meaning. It does identify both parameters by name and explains that `code` is Python executed in the opened `blend_file`, and that `result` should be a dict. However, it omits details about path formatting, execution environment, or constraints on the returned data, so it only partially compensates for the empty schema.

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 uses a specific verb+resource pair: 'Execute Python code in a background Blender process.' It clearly differentiates from interactive execution by specifying 'background' and the `blender --background` invocation, though it does not explicitly name or contrast the sibling `execute_blender_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?

The description implies usage for headless Blender execution but provides no explicit guidance on when to choose this tool over `execute_blender_code` or other siblings. There are no when-not-to-use conditions or alternative routing hints.

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