execute_python

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 behavioral disclosure. Arbitrary code execution is a high-risk operation with genuine destructive potential, yet the description says nothing about error behavior, execution context (bpy availability), synchronicity, side effects on the scene, or return value semantics. Even though an output schema exists, the agent is left blind to the risks of running 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 single sentence is efficient and front-loaded, with no wasted words. However, it is under-specified rather than appropriately concise for a tool of this power—conciseness earned through brevity, not through dense, high-information packing.

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 high complexity and risk of arbitrary code execution, paired with absent annotations and 0% schema coverage, this is critically incomplete. An agent has no way to know the execution environment, safety implications, or how to interpret results. For one of the most powerful tools in the set, the description provides almost no operational guidance.

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% and the description adds nothing about the `code` parameter. The agent gets no information about whether it should pass a full script, an expression, what modules/variables are in scope, or how to structure output. For a single-parameter tool with zero schema coverage, the description must fully compensate and it does not at all.

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 a clear verb-resource pair ('Execute arbitrary Python code') and the 'arbitrary' keyword explicitly marks this as the general-purpose escape hatch, distinguishing it from the 150+ specialized sibling tools. It avoids tautology, though it could more explicitly frame itself as the fallback for operations no dedicated tool covers.

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?

There is zero guidance on when to use this tool versus the many specialized siblings. With tools like set_transform, create_object, and add_modifier available, an agent needs to know this should be a last resort for uncovered cases, not a first choice. No conditions, no exclusions, no alternatives mentioned.

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