save_scene

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

The annotations provide no safety profile (readOnlyHint, destructiveHint false). The description discloses the copy behavior via newPath, but does not explicitly state whether saving without newPath overwrites the existing scene or what happens to the current scene state. This leaves some ambiguity for a mutation tool.

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 sentences, front-loaded with the main purpose and followed by usage guidance. No redundant filler, every sentence 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?

For a straightforward save tool with full schema coverage and no output schema, the description provides purpose, usage, and copy behavior. It is slightly incomplete in not detailing overwrite behavior, but overall adequate for the tool's simplicity.

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 covers 100% of parameters with descriptions. The description reiterates newPath's purpose (creating a copy), but does not add new meaning beyond the schema. The copy context is already in the schema, so baseline 3 is appropriate.

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 the tool saves a scene file, with an optional new path to create a copy. It distinguishes itself from sibling editing tools by noting that most editing tools save automatically, so this tool is primarily for saving copies.

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 says to use this primarily for saving copies, and that most editing tools save automatically, implying you don't need to save after typical edits. However, it does not name specific alternative tools, so the guidance is clear but not fully enumerating alternatives.

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