save_scene

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

No annotations, so the description carries the full behavioral burden. It does disclose the default path behavior (saves the current scene if no path is supplied), but says nothing about overwrite semantics, permission/file-write requirements, or whether an existing file is replaced without prompting.

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 front-loaded sentence with no filler; every word (verb, resource, optional-parameter role) earns its place.

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 an output schema present, return values need not be explained, and for a one-optional-parameter tool the description covers the essential call shape. Only the overwrite/error behavior is arguably missing.

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 single file_path parameter has no field description. The description partially compensates by explaining that the parameter is an optional target path for saving to a new file, but adds no format or overwrite details.

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 (save) and resource (the current Houdini scene), plus an optional variant (new file path). It is clearly distinct from the inverse sibling load_scene, though it does not explicitly name it.

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 versus load_scene or any alternative, nor prerequisites such as whether an unsaved scene must exist or whether a modified scene is required. The 'optionally' phrasing implies default behavior but no usage context is given.

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