create_scene

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

With no annotations, the description solely bears the burden of behavioral disclosure. It only states the basic action of creating a file, omitting side effects (e.g., overwriting, file permissions), error handling, or required project state. This is insufficient for a mutation 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 description is a single concise sentence with no wasted words. However, it could be more structured by separating the action from optional clarifications. It is front-loaded but too brief to fully inform.

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 the three parameters and no output schema, the description is incomplete. It fails to explain the significance of rootNodeType, whether the tool checks for existing files, or what return value to expect. More context is needed for reliable usage.

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 input schema has 100% description coverage, so the baseline is 3. The tool description adds no additional meaning beyond what the schema provides (e.g., no clarification of rootNodeType values or defaults).

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 'Godot scene file', directly indicating the tool's function. It distinguishes from sibling tools like instance_scene or add_node, which involve different operations. However, it lacks specificity about the content of the created scene (e.g., empty, with a root node), keeping it from a top score.

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 such as instance_scene or create_script. It does not mention prerequisites (e.g., project must exist) or scenarios that favor this tool, leaving the agent without contextual cues.

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