godot_save_scene

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

The description does add the key behavioral fact that saving writes the edited scene to disk, which the annotations alone do not fully convey. It does not, however, explain overwrite behavior, failure modes, or whether saving with a new path changes the active scene's path, though the schema covers some of this.

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, focused sentence with no filler. The key verb and resource are front-loaded, and every word adds meaning.

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 save operation whose parameters and output format are documented in the schema, the description is sufficiently complete. It could have mentioned the alternative of saving to a specified path, but the schema's parameter description already covers that scenario.

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 description itself does not mention either scene_path or response_format. However, the input schema already provides meaningful descriptions for both parameters, including the 'If None, saves active scene in place' behavior, so the description's omission is not a major gap.

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 action ('save') and resource ('currently edited scene') in a way that is distinct from siblings like godot_open_scene or godot_create_scene. However, it does not explicitly name any alternative or call out the difference from similar scene-related tools, so it falls just short of 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 usage context is implicitly clear: an agent should call this when it wants to persist the current scene. However, there is no explicit guidance about when to use this tool versus alternatives, nor any exclusions or conditions regarding paths or in-place saves.

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