save_timeline

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 disclose two real behavioral traits: the operation writes a new file rather than importing, and the project is renamed by default to avoid clashing. It does not say whether an existing file at the output path is overwritten, whether Final Cut must be running, or what the call returns.

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 sentences, no filler, with the core action and non-import behavior front-loaded and the rename safeguard second. Every clause earns its place.

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 two-optional-parameter write tool with no annotations and no output schema, the description covers intent and one default but leaves the return value, overwrite semantics, and prerequisites unaddressed. Adequate to call it, not complete enough to predict its effects.

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 0%, so the description must compensate. It does explain the project_name default ('<name> (Claude edit)') and implies output_path via '.fcpxml (or .fcpxmld)', but neither parameter's format is specified — no guidance on whether output_path is a file or directory, or what happens when it is omitted (both params are 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?

States a specific verb and resource ('Save the edited timeline') plus the exact artifact produced (a new .fcpxml/.fcpxmld file) and the key qualifier 'without importing it'. This separates it from file-reading siblings like open_timeline and fcp_import_xml, though it never names the closest alternative, fcp_export_project.

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?

Usage is only implied: the phrase 'edited timeline' and 'without importing it' suggest calling this after edits to persist work to disk rather than pushing into Final Cut. There is no explicit when-to-use statement and no routing to fcp_export_project or send_to_final_cut, which the agent must disambiguate on its own.

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