fcpxml_split_clip

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

No annotations exist to disclose safety or destructive behavior. The description does not mention what happens to the original file, whether the output is a new file or overwrites, or error conditions. The optional output_path is unexplained.

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, using a clear bulleted list for arguments. Every word earns its place without repetition.

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 presence of an output schema (not shown), the description covers the basics but lacks details on return values and differences from the sibling fcpxml_trim_clip. Adequate but not comprehensive.

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 adds meaningful explanations for all four parameters, including the format hint 'FCPXML time' for split_at.

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 'split' and the resource 'clip in a .fcpxml file'. It distinguishes from sibling tools like fcpxml_trim_clip by using 'split' instead of 'trim'.

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 guidance is provided on when to use this tool versus alternatives such as fcpxml_trim_clip. There is no mention of prerequisites, when not to use, or context for when splitting is appropriate.

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