execute_code

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

With no annotations, the description discloses the environment (bpy, mathutils, math, os), blocked imports, and the expected return method. It omits potential risks like crashes or security, but still provides substantial transparency.

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?

Four concise sentences front-loaded with purpose, then environment, restrictions, and usage. Every sentence adds unique value with 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?

For an arbitrary code execution tool with no output schema, the description covers what it does, what's available, what's blocked, and how to return results. It could mention error handling or execution limits but is largely sufficient.

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 single 'code' parameter has 0% schema description coverage. The description adds significant context: available modules, blocked imports, and instructions to store results in 'result' variable. This fully compensates for the schema gap.

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 inside Blender' and specifies the environment and blocked imports. It distinguishes itself from sibling tools by saying 'Use this for advanced operations not covered by other tools.'

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 advises using this tool when other tools don't cover the operation. It implies when not to use it (when other tools suffice), but it could be more explicit about avoiding simple tasks.

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