save_scene

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds the save-as context but doesn't disclose further behaviors like overwrite behavior or error conditions, which is acceptable given the simple nature of the 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 short sentences deliver both the primary function and the parameter usage with zero redundancy. The description is perfectly sized for the tool's simplicity.

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 tool with one optional parameter and no output schema, the description explains what the tool does and how to use the parameter. It doesn't describe return values or edge cases, but these are not essential for such a simple operation, making the description complete enough.

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, and it does by explaining that 'path' is the res:// destination for save-as. This gives the parameter meaningful context beyond just a type, though it doesn't explicitly state that the parameter is optional.

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 the specific verb 'Save' with the resource 'the scene currently open in the editor', clearly distinguishing it from sibling tools like open_scene, play_scene, and instance_scene. It also explicitly mentions the save-as behavior, which differentiates it from a plain save.

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?

It clearly states when to use the optional 'path' parameter for save-as, implying that omitting it performs a regular save to the current scene path. It doesn't explicitly name alternatives or exclusions, but the context is clear and sufficient for basic usage.

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