fcpxml_fix_flash_frames

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

No annotations provided. The description mentions extending short clips but does not disclose side effects (e.g., file modification, preservation of other edits) or limitations. Lacks behavioral depth.

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 a single-line summary plus a bulleted argument list, no redundant text. Front-loaded with action verb, each sentence 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?

Explains all parameters and overall action. Output schema exists, so return values likely covered. No mention of error handling or integration with detect_flash_frames, but adequate for a simple tool.

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 coverage is 0%, but the description's Args section explains each parameter's role (path, min_frames, frame_duration, output_path) with clear, concise descriptions, adding necessary context beyond schema defaults.

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 name and description clearly state the tool's purpose: auto-fix flash frames by extending very short clips. It distinguishes itself from sibling 'fcpxml_detect_flash_frames' which only detects, not fixes.

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 explicit when or when-not to use, nor alternatives. The description implies usage after detecting flash frames, but lacks direct guidance or mention of prerequisites.

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