Create a new scene

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

With no annotations, the description fully discloses key behaviors: name slugification, collision suffixes, type change resetting config, default size, scrolling, and lack of background creation. No contradictions.

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?

Concise paragraph with no wasted words. Front-loaded with main action, each sentence adds value. Length is appropriate for the tool's complexity.

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?

Comprehensive for most aspects but does not describe return values. No output schema exists, so noting what the tool returns would improve completeness. Otherwise covers behavior well.

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?

Adds significant meaning beyond the input schema: name slugification/collision, type uppercase requirement and consequence, default size and scrolling, backgroundId usage. Schema coverage is 100% but description enriches every parameter.

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 it creates a new scene folder and file, differentiating it from sibling tools like read_scene, delete_scene, and list_scenes. It specifies the location and naming behavior.

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?

Provides guidance on scene type selection (must be uppercase, deliberate choice due to engine config reset) and background handling (not created, must be provided or added later). Lacks explicit when-not-to-use but offers solid context.

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