Create Godot Project

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

With no safety annotations beyond the title, the description carries the full disclosure burden. It explicitly reveals that files are written, that Godot's editor runs in headless import mode when both conditions hold, and that this is the engine's initialization step. It stops short of stating overwrite behavior or failure handling, which are relevant for a write tool.

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 core purpose is front-loaded in the first sentence, and the second sentence provides the only necessary nuance: the conditional import behavior. Both sentences earn their place with no filler or redundant restatement.

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 an 8-parameter tool with full schema coverage and an output schema, the description is largely sufficient: it explains the artifact, the optional external process, and the prerequisite environment variable. Remaining gaps such as overwrite behavior and failure handling are real but minor given the existing structured field coverage.

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 100%, so the baseline is 3. The description adds extra meaning for run_godot_import by tying it to GODOT_MCP_ALLOW_GODOT_EXEC=1, and for relative_path by anchoring it under the workspace. No other parameter needs description-level supplementation.

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-resource pair (create a Godot project) and names the exact artifacts written (project.godot and a starter .tscn), which clearly distinguishes it from sibling tools like godot_create_scene or godot_create_script. It leaves no ambiguity about what this tool produces.

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?

It clearly frames the use case: creating a project under the MCP workspace, mirroring what the Project Manager does on disk. However, it does not explicitly say when not to use it or point to alternatives such as godot_refresh_project for existing projects, so exclusions are left to inference.

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