Re-save a scene

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety is largely covered structurally. The description still earns credit by disclosing behavior the annotations do not: the scene is round-tripped through Godot, the file is normalized, and supplying newPath converts an overwrite into a copy.

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?

A single sentence, front-loaded with the core action and appending the optional-path behavior without padding. Nothing redundant.

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?

With only three simple parameters, full schema coverage, and no output schema, the description covers the operation and its two modes (overwrite vs copy) adequately. It omits return/confirmation behavior, but that is a minor gap for a mutation tool of this simplicity.

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 slightly exceeds the schema by explaining that newPath creates a copy/variant rather than just a destination, adding intent beyond the field description 'Save a copy here instead of overwriting.'

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?

States a specific verb+resource ('load and re-save a scene through Godot') and adds the notable effect that the file is normalized, which distinguishes it from plain reads like get_scene_tree. It does not explicitly contrast with the sibling create_scene, which is the closest point of confusion.

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 phrase 'optionally to a new path to make a copy/variant' implies the copy use case, which is useful context for newPath. However, there is no explicit statement of when to use this versus create_scene or get_scene_tree, and no preconditions are given.

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