create_scene

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

With no annotations, the description carries full burden for behavioral traits. It only states the action without revealing side effects (e.g., whether it overwrites an existing file at the path), required permissions, or default behavior for the root_node_type parameter. The term 'empty scene' is vague regarding initialization details.

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 a single, well-structured sentence that front-loads the core purpose. Every word contributes meaning without redundancy.

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 tool with 2 parameters and no output schema, the description is mostly adequate. It explains the main action and the parameter from schema, but could benefit from clarifying what 'empty scene' entails (e.g., default root node if not specified). Still, it's nearly complete given low complexity.

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 coverage is 100%, so the schema already documents both parameters with descriptions. The description adds minimal extra meaning ('empty scene') but does not provide examples or clarify default values for root_node_type. Baseline 3 is appropriate since schema does the heavy lifting.

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 purpose: 'Create a new empty scene with a specified root node type'. It uses a specific verb ('create') and resource ('scene'), and distinguishes from sibling tools like 'add_node' or 'open_scene' by emphasizing 'empty' and 'specified root node type'.

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 no guidance on when to use this tool versus alternatives (e.g., 'add_scene_instance' for instantiating existing scenes). It lacks context about prerequisites, such as whether the target directory must exist, or when to use 'create_scene' vs 'open_scene' or 'save_scene'.

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