godot_create_scene

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

The description mentions 'save to disk,' consistent with readOnlyHint=false, but fails to disclose other behaviors such as whether it opens the scene in the editor (controlled by open_in_editor), whether it can overwrite existing files, or if it creates directories. Annotations provide only minimal safety hints, and the description adds little beyond the obvious write action.

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, direct sentence that front-loads the primary purpose. There is no wasted wording, and it is appropriately concise for the information it conveys.

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 description is insufficient for a tool with multiple parameters and side effects. It omits critical usage context such as overwriting, opening the editor, and differentiating from scene-modification tools. Although an output schema exists, real-world scenarios (e.g., whether to use this vs. godot_create_node) are not addressed, leaving gaps for an agent to reason about.

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 tool description contains no parameter information at all, and schema description coverage is reported as 0%, meaning the description does not compensate for the schema. With multiple parameters (root_name, root_type, properties, scene_path, open_in_editor, response_format), an agent must rely entirely on the schema, which is not enhanced. The description fails to explain how parameters relate to the tool's 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 explicitly states 'Create a brand new scene file with root node and save to disk,' which identifies a clear verb, resource, and key details. This differentiates it from sibling tools like godot_open_scene, godot_instantiate_scene, and godot_create_node, making its purpose unambiguous.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention that it creates a new file (vs. modifying existing scenes), does not address overwriting behavior, and provides no exclusions or comparisons with siblings. An agent must infer usage from the name alone.

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