blender_execute_python

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

Annotations already provide destructiveHint: true, readOnlyHint: false, openWorldHint: true. The description reinforces the dangerous nature ('may modify the scene or perform dangerous operations'), adding useful context but not going beyond what annotations already convey. The return is vaguely described as 'Execution result'.

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?

Extremely concise – two sentences plus structured Args/Returns. Front-loaded with purpose and caution. No wasted words.

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?

Despite being a powerful and potentially dangerous tool, the description lacks details on execution context (Blender API access, error behavior), return value format (despite an output schema existing), and specific usage scenarios. The caution is helpful but incomplete for safe use.

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 description's 'Args: params: Python code and timeout' merely restates parameter names from the schema, which already includes brief descriptions. With schema_description_coverage effectively high (schema fields have descriptions), the description adds zero new semantic meaning.

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 Python code in Blender' – a specific verb and resource. This distinguishes it from sibling tools that perform discrete Blender operations (create, delete, transform).

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 includes a caution about modifying the scene, implying careful use, but does not provide explicit when-to-use/when-not-to-use criteria or alternatives. No guidance on when to rely on this tool versus other specific operations.

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