save_scene

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

Annotations provide no readOnlyHint or destructiveHint, so the description must convey behavioral traits. It merely states 'save changes' without explaining if it overwrites, creates backups, requires the scene to be open, or has any side effects. Minimal transparency 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?

The description is extremely concise (5 words), which is efficient for a simple operation. However, it could be slightly longer to include useful context like 'Saves modifications to an existing scene file' without being verbose.

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 performs a save operation (mutation) with no output schema and minimal annotations, the description lacks completeness. It does not mention return values, error conditions, or prerequisites (e.g., scene must exist). Important gaps for an agent to use correctly.

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?

Input schema covers all three parameters with descriptions, achieving 100% coverage. The description adds no additional parameter meaning beyond the schema, so 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 'Save changes to a scene file' uses a specific verb ('Save') and resource ('scene file'), clearly indicating the action. It distinguishes from siblings like 'create_scene' or 'read_scene' by focusing on saving changes to an existing scene.

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 explicit guidance on when to use or when to avoid, nor mentions of alternatives among siblings. The description implies usage for persisting modifications to a scene, but lacks context like prerequisites or conditions.

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