scene_save

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

No annotations provided, so the description must fully disclose behavior. It states 'Save changes' but does not clarify whether the tool overwrites existing files, requires a previously saved or loaded scene, or what happens if the project_path is invalid. The optional new_path hint adds minimal context.

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?

Description is fairly concise but includes an 'Args' section that duplicates parameter info present in the input schema. Could be streamlined to avoid redundancy. Front-loads the main action clearly.

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 no annotations, 0% schema coverage, and an output schema (though undocumened), the description should cover return values, error conditions, or side effects. It omits whether the tool returns success/failure, what happens if scene_path doesn't exist, or any authorization requirements.

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%, so the description must compensate. It explains parameter meanings: project_path (directory), scene_path (relative), new_path (optional for variant creation). This adds value beyond the schema's type-only definitions, but no details on expected formats or constraints.

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?

Description clearly states 'Save changes to a scene file' and lists parameters with brief explanations. It distinguishes from siblings like scene_create (new scene) and scene_instantiate, but does not explicitly differentiate from scene_get_tree or other scene-related tools.

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 versus alternatives such as scene_create (for new scenes) or scene_instantiate (for instantiating inherited scenes). The description lacks context about prerequisites (e.g., scene must be open) or when to use new_path for variants.

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