execute_blender_pass

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

With no annotations, the description carries the full burden. It usefully discloses headless execution, the sentinel verification contract, and that the response includes returncode and stdout snippet. However, it omits critical runtime traits such as timeouts, side effects of scripts (e.g., writing to .blend files), and what happens when Blender is unavailable or the sentinel is missing.

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 front-loaded with the core action and verification contract, followed by efficient Args and Returns sections. The Returns section partially duplicates the output schema, but the content remains short and earns its place.

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 not be fully explained. Still, for a code-execution tool with no annotations, the definition should cover prerequisites (Blender availability), failure modes, and isolation/side-effect behavior; those gaps leave the agent to infer important runtime context.

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, and it does: script_path is defined as the Python script executed inside Blender, and blend_path is explained as an optional existing .blend file to open. It adds real meaning beyond the bare schema, though it does not state format constraints or requiredness explicitly.

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?

States a specific verb and resource — execute a bpy Python script in headless Blender — plus a verification step tied to the AGENT_OK sentinel contract. This is clearly distinct from the sibling tools (validate_part_spec, blender_runtime_status, query_blender_knowledge) even without naming them.

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 never says when to use this tool versus alternatives. It does not mention checking blender_runtime_status first, nor does it explain when a caller should prefer this execution tool over validation or knowledge-query siblings.

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