create_scene

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

The description does not disclose behavioral details such as whether an existing file at scenePath will be overwritten, what permissions are needed, or what happens if the project path is invalid. Annotations are all false, which only signals that this is not a read-only operation, leaving the agent without clarity on side effects.

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 exactly two sentences: the first states the core purpose, and the second clarifies the key parameter and default. It is front-loaded, free of filler, and every sentence earns its place.

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 relatively simple tool with three parameters and a 100% schema description coverage, the description covers the essentials. Its main gap is not explaining return values or what happens if the scene file already exists, but the schema and simplicity keep it mostly complete.

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 schema already covers all parameters, but the description adds a valuable default value for rootNodeType ('Node2D') and examples ('Node2D', 'Node3D', 'Control'), providing semantic detail not present in 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 states a specific verb ('Create'), a specific resource ('Godot scene (.tscn) file'), and the scope ('with a root node'). The word 'new' distinguishes it from tools like save_scene or add_node, making its purpose unambiguous relative to siblings.

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 implies the primary use case (creating a new scene file) but provides no explicit guidance about when to use this tool versus alternatives like add_node or save_scene. It does not mention exclusions or alternatives, so usage context is inferred rather than stated.

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