fcpxml_batch_apply_transition

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

No annotations are provided, so the description carries full burden. It only states the basic action without disclosing side effects (e.g., whether it overwrites existing transitions, handles gaps, or modifies in place). The output_path parameter suggests a new file is created, but this is not explicitly stated.

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 concise with one sentence for purpose and a structured Args list. It is front-loaded and efficient, though the Args section is somewhat redundant given the schema, but it adds needed context due to lack of schema descriptions.

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?

Despite having an output schema, the description leaves significant gaps: no explanation of duration syntax, valid transition names, behavior on missing output_path, or error conditions. For a batch editing tool, this is insufficient for an agent to invoke 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?

The input schema has 0% description coverage. The Args section adds basic meaning (e.g., path is to .fcpxml file, duration is transition duration), but lacks details like duration format, valid transition names, or behavior when output_path is empty. This partially compensates but not fully.

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 tool adds transitions between all adjacent clips in the timeline. This is a specific verb+resource combination and distinguishes it from siblings like fcpxml_add_transition (singular) and other batch tools.

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 description implies usage by stating the action, but it does not provide explicit guidance on when to use this tool versus alternatives like fcpxml_add_transition. No exclusions or prerequisites are mentioned.

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