save_scene

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

With no annotations provided, the description must carry the full weight of behavioral disclosure. It only says 'Save the current scene,' implying a write operation but not detailing overwrite behavior, return values, or failure modes. It does not mention whether saving to a new path creates a file or how existing files are handled.

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?

Two concise sentences, with the core purpose front-loaded and the parameter guidance following. Every word earns its place, and the structure is immediately scannable.

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 simple save operation with one optional parameter, the description covers the essential action and parameter semantics. But it omits differentiation from the export sibling, potential side effects like overwriting, and any expected return value. Given no annotations, this leaves gaps that an agent might need to infer or test.

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 clarifies the only parameter beyond the schema's bare 'Path' field: 'Omit path to save in place' indicates that providing a path saves to that location and omitting it saves in place. This adds meaningful semantic context that the schema lacks, compensating for the 0% schema coverage.

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 states a clear action and resource: 'Save the current scene.' This distinguishes it from most siblings like apply_material or create_object. However, the presence of an 'export' sibling introduces potential ambiguity, as 'save' and 'export' can overlap, but the description does not address this distinction.

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 only usage guidance is 'Omit path to save in place,' which instructs on parameter use but offers no context on when to prefer this tool over alternatives like export. It does not specify prerequisites, scenarios, or conditions for selection, leaving the agent to infer when saving is appropriate.

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