save_project_as

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

With no annotations, the description carries the full burden, and it does add real value: overwrite protection ('Existing files are refused'), the media-free nature of .RTrackTemplate exports, and a gate precondition. It stops well short of describing what the fx_* and track-targeting parameters actually mutate, and gives no auth/permission or response detail.

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?

Three short sentences, front-loaded with the two outcome modes, then the safety constraint and precondition. Every clause earns its place with no filler.

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 12-parameter mutation tool with no annotations and no output schema, the description covers the core modes and one safety rule but leaves too many parameters and mode interactions (fx targeting, dry_run behavior, template toggling) to inference.

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 only 42% across 12 parameters, so the description needs to compensate. It clarifies that 'path' must be new/absolute and that tracks are 'explicitly named', but leaves fx_guid, fx_index, fx_scope, template, track_guids and use_selected_track essentially unexplained beyond their bare schema entries.

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?

States a specific verb and two distinct resource outcomes ('Save to a NEW absolute .rpp path' vs 'export explicitly named tracks as a media-free .RTrackTemplate'), which lets an agent tell it apart from generic save tools. It is slightly clouded by the presence of fx_guid/fx_index/fx_scope parameters that the description never ties into either mode.

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 'or export...' phrasing implies the two selection modes, and 'Requires project save gate' names a precondition. However, no sibling alternative is named and no guidance is given on when to prefer a plain project save versus a template export, or when the fx_* parameters apply.

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