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 burden of behavioral disclosure. It states 'Save changes' which implies a write operation, but doesn't specify if this overwrites the original file, requires specific permissions, handles errors (e.g., invalid paths), or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core action ('Save changes to a scene file') with zero wasted words. It's appropriately sized for a straightforward tool, making it easy for an agent to parse quickly.

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 tool involves file mutation (saving changes) with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, side effects, or return values, which are crucial for an agent to use this tool correctly in a Godot project environment.

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 description coverage is 100%, with clear descriptions for all three parameters in the input schema. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain the relationship between 'scenePath' and 'newPath' or provide examples). Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Save changes') and resource ('to a scene file'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'create_scene' or 'update_project_uids', which might involve similar file operations in a Godot context.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., if the scene must be loaded or edited first), exclusions, or how it differs from tools like 'create_scene' or 'update_project_uids', leaving the agent to infer usage from context alone.

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