save_scene

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

The description lacks crucial behavioral details: it does not specify whether the save overwrites existing files, creates new ones, or if any destructive actions occur. Since no annotations are provided, the description should cover these aspects, but it fails to do so.

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?

The description is a single short sentence with no unnecessary words. It is efficiently front-loaded, but could be slightly more structured to improve clarity.

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?

Given the low complexity (one optional parameter, no output schema), the description is adequate but incomplete. It does not explain what 'current scene' means, and lacks behavior details, making it only minimally sufficient.

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 schema covers the single parameter with 100% description coverage. The description adds minimal value beyond the schema, merely repeating the idea of 'save to a new path'. Baseline score of 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 action ('save') and the resource ('scene'), and it distinguishes this tool from siblings like 'open_scene' or 'create_scene'. However, it could be more explicit about the context (e.g., saving the scene currently open in the editor).

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?

No guidance is provided on when to use this tool versus alternatives such as 'save_game_state' or 'save_editor_layout'. The description does not mention conditions, prerequisites, or when not to use it.

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