scene_create

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

No annotations provided. The description only states creation without disclosing behavior such as overwrite policy, required permissions, or side effects like file system changes.

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 two lines for purpose and three lines for parameters. However, the 'Category: Scene' line is unnecessary and could be removed for tighter structure.

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?

No information about the output (return value) despite having an output schema. Missing details about file overwrite, directory creation, or error conditions. The description is incomplete for a file creation tool.

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 has 0% description coverage (no parameter descriptions), but the description fully compensates by explaining each parameter: project_path (project dir), scene_path (relative save path), root_node_type (with examples Node2D, Node3D). This adds significant value beyond the schema's plain type information.

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 'Create a new Godot scene file', specifying the verb 'create' and resource 'scene file', which is distinct from sibling tools like scene_instantiate, scene_list, scene_save, etc.

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?

No guidance on when to use this tool vs alternatives (e.g., scene_instantiate or scene_create compared). No when-not or prerequisite conditions mentioned.

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