save_scene

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

Discloses overwriting silently, returns plain-text confirmation, and errors if file doesn't exist. The idempotentHint annotation is consistent; no contradiction. Could add more about data loss, but sufficient.

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?

Three concise sentences, front-loaded with purpose, then usage, then outcomes. No wasted words, easy to parse.

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 tool with 3 params, no output schema, the description covers purpose, when to use, behavioral outcomes, and error conditions. Complete and self-contained.

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 has 100% coverage, so baseline 3. The description adds context for newPath as save-as function, and clarifies the role of scenePath. Provides value beyond schema.

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 it repacks and saves a scene, optionally to a new path (save-as). It distinguishes from auto-saving mutations, making the tool's specific purpose unambiguous.

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?

Explicitly states that most mutations auto-save, so this tool should only be used for save-as via newPath or to re-canonicalize hand-edited files. Provides clear when-to-use and when-not guidance.

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