create_scene

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

Discloses that the tool saves automatically and overwrites silently if the file exists, adding behavioral context beyond the idempotentHint annotation, with no contradictions.

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 concise with four sentences that front-load the purpose, then cover usage, parameter defaults, and behavioral details without extraneous words.

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 tool's complexity, presence of output schema, and annotation coverage, the description fully covers purpose, usage, parameters, and behavior, leaving no gaps.

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?

While the input schema already describes parameters, the description adds the default for rootNodeType and suggests appropriate values for 3D or UI scenes, enhancing parameter semantics.

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 tool creates a new Godot scene file with a single root node, distinguishing it from sibling tool 'add_node' by explicitly noting when to use each.

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?

Explicitly advises using this tool when starting a new scene from scratch, and directs users to 'add_node' for adding nodes to an existing scene, providing clear usage context.

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