save_scene

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

No annotations are provided, so the description carries the full behavioral burden. It only states the write action and omits material behavior for a persistence operation: whether an existing file gets overwritten, whether the scene must be non-empty, whether the operation is reversible, and whether it mutates the in-memory scene state.

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 13-word sentence with no filler; the verb and resource are front-loaded. A minor deduction because 'at path' reads as truncated phrasing that could be clearer ('to the specified path'), but the sentence remains efficient.

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?

The tool is simple (1 parameter, output schema present) and the description covers the core action and destination. But for a mutation operation with zero annotation coverage, the missing overwrite semantics and preconditions (e.g., a scene must be composed before saving) keep it from being fully self-sufficient. Adequate, with clear gaps.

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 coverage is 0%, so the description must compensate for the sole 'path' parameter, and it partially does: 'Write ... to a .glb file at path' clarifies that path is the destination file location. However, it leaves ambiguity about whether parent directories are created, whether the .glb extension is enforced, and what path formats are accepted.

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 uses a specific verb ('Write') and identifies a precise resource ('current composed scene') and target format ('.glb file at path'). This lets an agent instantly distinguish it from siblings like load_scene, render_scene, and get_scene_info without opening any schema.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention of the natural inverse workflow (load_scene) or the sibling render_scene for visual output. Usage is only implied by the verb and resource; no conditions or recommended scenarios are stated.

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