execute_blender_code

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

With no annotations provided, the description carries the full burden. It only states the tool executes code but does not disclose potential risks (e.g., destructive changes), prerequisites, or side effects. This is insufficient for an arbitrary code execution tool.

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 extremely concise: two lines of prose plus parameter list. It is front-loaded with the main purpose, and every sentence adds value.

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, the description is severely lacking. It does not mention prerequisites (e.g., Blender running), error handling, return values, or safety considerations. The completeness is inadequate even with the parameter descriptions.

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. It briefly explains each parameter: 'code: The Python code to execute' and 'user_prompt: The original user prompt... for telemetry'. This adds meaning beyond the schema's type/default, though it is minimal.

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 in Blender', specifying both the action (execute) and the resource (Python code in Blender). This distinguishes it from sibling tools which focus on assets and queries.

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 to 'do it step-by-step by breaking it into smaller chunks', providing a usage hint. However, it lacks explicit when-to-use vs. alternatives, and does not mention when not to use this tool.

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