open_timeline

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

With no annotations, the description carries the full burden. It usefully discloses return behavior ('Returns a summary and the clip list') and the conditional project-selection behavior, but says nothing about whether loading replaces the current timeline state, how a missing/ambiguous project name is handled, or error conditions for a state-affecting load.

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 core action, then the conditional case, then the return value. Nothing is wasted.

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?

With no output schema, the description's return-value sentence is necessary and present, and both params are explained. The main omission is the side effect on existing timeline state, which matters for a load operation.

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, and it largely does: it explains that 'path' accepts either a file or a .fcpxmld bundle and that 'project' is used to pick one by name when the file holds several projects. It lacks specifics on project-name matching, but both params gain real meaning.

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 (Load) and resource (exported FCPXML file or .fcpxmld bundle) with the 'for editing' purpose. It's clear what the tool does, but it doesn't explicitly distinguish itself from siblings like fcp_import_xml or get_timeline, so sibling differentiation is left to inference.

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?

'for editing' implies the intent, and the project-selection sentence covers the multi-project case. But there's no explicit when-to-use this versus fcp_import_xml or get_timeline, and no stated prerequisites (e.g., that the file must already be exported).

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