blender_scene_create

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

Annotations provide no safety profile (all hints false). The description does not disclose critical behavioral details such as whether creation fails on duplicate name, overwrites, or depends on an open Blender file. It only states the basic action without side effects or prerequisites.

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 concise at three sentences plus structured Args/Returns. The main point is front-loaded. Slight deduction for including redundant parameter descriptions that repeat the schema.

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 a simple creation tool, the description covers the basic purpose and parameters, but lacks specifics about error behavior, naming rules, or the structure of the return value. Given the output schema exists but is not detailed, the description could do more.

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 schema description coverage at 0%, the description should compensate by adding meaning. However, it merely restates 'scene name and optional copy source' which adds no value beyond the schema's property descriptions. No examples, constraints, or formatting hints are provided.

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 'Create a new scene in Blender' with a specific verb and resource. It mentions optional copying from an existing scene, distinguishing it from sibling tools like blender_scene_delete or blender_scene_list.

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?

No guidance on when to use this tool versus alternatives, such as when to create a new scene vs. copy from an existing one, or handling duplicate names. The 'optionally copied' hint is too minimal to be considered explicit usage guidance.

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