create_scene

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

With no annotations, the description carries the full burden of explaining behavior. It only states 'Create a new scene,' implying a write operation, but discloses no side effects such as whether it replaces the current scene, creates a file, or requires saving existing work.

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 brief, which could be acceptable for a trivial tool, but under-specification is not conciseness. It lacks structure and fails to earn its place by omitting necessary details like parameter explanations.

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 operates in a rich editor context with many siblings, but the description gives no context about how a new scene is created, what root_type options exist, or what happens after creation. It is completely inadequate for a tool with two undocumented parameters and no output schema.

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 description coverage is 0%, and the description does not mention the parameters 'name' or 'root_type' at all. It fails to provide any meaning or syntax beyond the bare property names, leaving the agent guessing about their purpose.

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 verb 'create' and the resource 'scene', making the primary action unambiguous. It distinguishes from siblings like open_scene, save_scene, and close_scene through the 'create' verb, though it doesn't elaborate on what a new scene entails.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, project context, or scenarios where create_scene is preferred over 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.