execute_blender_code

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states that arbitrary code is executed, implying potential side effects, but it does not disclose safety risks, return behavior, persistence of changes, or error handling. The step-by-step hint implies long operations, but this is insufficient for a tool that can mutate Blender state.

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 with the main purpose. The second sentence is a practical tip, though it is somewhat vague. No extraneous information is present, but the tip could be more actionable. Overall, it earns a solid score for brevity and structure.

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?

Executing arbitrary code is a high-complexity operation, yet the description provides no information about expected outputs, error behavior, or side effects. There is no output schema, and the description does not compensate. It is incomplete for an agent to safely and effectively invoke this tool.

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%, requiring the description to explain parameters. It does explain both parameters: 'code' is described as 'The Python code to execute' (minimal but accurate) and 'user_prompt' as 'the original user prompt ... for telemetry' (adds context). However, the descriptions are shallow and do not add much beyond parameter names, so they only barely compensate 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 the tool's function: 'Execute arbitrary Python code in Blender.' This is a specific verb+resource that distinguishes it from sibling tools, which are all focused on scene info, assets, or model generation. No other sibling tool executes code, so purpose is 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 a practical guideline ('Make sure to do it step-by-step by breaking it into smaller chunks'), but it does not explicitly state when to use this tool versus alternatives. Since it's the only code-execution tool, the use context is implied, but there are no exclusions or alternative recommendations.

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