fcpxml_add_marker

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

No annotations provided. The description mentions output_path with a default suffix, but does not clarify that the original file is unchanged or any other side effects.

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?

Purpose is front-loaded, but 'Args:' header adds redundancy for schema-aware agents. Could be more concise.

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?

Covers basic parameters but lacks details on marker_type behavior, clip existence checks, or output file implications. 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 coverage is 0%, so description adds meaning with parameter explanations (e.g., time format example, marker_type options) beyond the schema's type/default.

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 states 'Add a marker to a clip' with a specific verb and resource, distinguishing it from sibling tools like fcpxml_add_keyword or fcpxml_add_title.

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 on when to use this tool vs alternatives like fcpxml_batch_add_markers, nor prerequisites (e.g., existing clip in an fcpxml file).

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