save_scene

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

With no annotations, the description must carry the burden of behavioral disclosure. It reveals that the tool writes a scene file and can use an alternate path, but does not say whether it overwrites existing files, whether the scene must already exist, whether directories are created, or whether the operation is reversible.

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 one purposeful sentence followed by a terse parameter list with no filler. The core behavior is front-loaded, and every line adds information.

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 a three-parameter file-writing tool, the description covers the invocation inputs but leaves open important context: whether saving is destructive/overwriting, whether the scene must already exist, and what the output indicates. The presence of an output schema reduces the need to document return values, but the missing mutation semantics keep this from being fully complete.

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 0%, and the description compensates by explaining all three parameters: absolute project_path, relative scene_path, and conditional new_path. It stops short of specifying behavior like what happens when new_path is empty, but it adds meaning the schema lacks.

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 opening sentence, 'Save (or save-as) a Godot scene file', names a specific action and resource, and the save-as variant is explicit. This distinguishes it from siblings like create_scene and add_node without needing their schemas.

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 statement about when to choose this tool over alternatives such as create_scene or load_sprite. The parameter list implies a save workflow, but there are no conditions, exclusions, or explicit routing.

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