generate_scene_script

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

Despite no annotations, the description explicitly states 'WITHOUT executing it' and explains the output is a script for review or manual execution. This clearly communicates the read-only, non-destructive behavior. It lacks details on error handling or permissions, but for a non-executing script generator, the key behavior is well-disclosed.

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 with two sentences, no redundancy, and front-loaded key information. Every word is necessary and contributes to understanding the tool's purpose and output.

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 tool has an output schema (not shown in detail) and no annotations, the description adequately explains the return value as a script string. However, it omits details about what the script contains, how to interpret it, or potential limitations, leaving some gaps for a tool that generates code.

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?

With 0% schema description coverage, the description adds moderate value by referencing 'JSON scene description' and directing to build_scene_from_json for format details. This gives context beyond the raw schema but does not comprehensively explain the parameter's expected structure or constraints.

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 generates a bpy Python script from a JSON scene description without executing it, using a specific verb and resource. It distinguishes from the sibling 'build_scene_from_json' by referencing it for the JSON format, but does not explicitly differentiate from other script-execution 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 provides minimal usage guidance: it directs users to 'build_scene_from_json' for the JSON format, implying a workflow dependency. However, it does not specify when to use this tool versus alternatives like execute_code or execute_script_headless, nor does it offer exclusion criteria.

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