create_scene

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

With no annotations provided, the description should disclose behavioral details. It only states the basic action without mentioning side effects, such as whether the new scene becomes the current one, if it opens in the editor, or any required permissions. The agent cannot infer execution 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 extremely concise (four words), which aids quick reading, but it is too sparse to provide adequate information. It loses points for being under-specified rather than appropriately sized.

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?

Given that the tool has two parameters with no schema descriptions and no output schema, the description should elaborate on creation behavior and return value. The current description only covers the high-level purpose, leaving significant gaps in understanding for an AI agent.

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 omits any explanation of the two parameters ('scene_name' and 'root_node_type'). The agent has no information about the format or allowed values for 'scene_name' (e.g., path vs. name) or the purpose of 'root_node_type'.

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 'Create a new scene file' clearly states the verb 'Create' and the resource 'scene file', distinguishing it from sibling tools like 'open_scene' or 'save_current_scene' which perform different actions on scenes.

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, nor any prerequisites or exclusions. It does not mention that it is for creating a new scene from scratch, which could be inferred but is not explicit.

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