create_scene

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

The description only states the basic create action with no disclosure of behavioral traits such as overwrite behavior, parent directory creation, or project context. Since annotations are absent, the description carries the full burden but provides minimal insight.

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 sentence, highly concise and front-loaded with the verb. There is no wasted text.

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?

The tool is a mutating operation without annotations or output schema. The description does not explain what 'from template' means beyond the schema, nor does it specify file overwrite or directory creation behavior, leaving potential ambiguity for correct invocation.

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 adds no information about parameters; however, the input schema has 100% description coverage, so the schema already documents path, template, and root_name. The description neither conflicts with nor adds to the schema.

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 creates a new scene from a template, using a specific verb and resource. It distinguishes from other create_* tools by focusing on scenes, though it does not explicitly differentiate from sibling tools like editor_create_scene.

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?

There is no guidance about when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or cases where another tool would be more appropriate.

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