add_camera_cut_track

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

Beyond the boolean hints, the description discloses genuinely useful behavior: get-or-create semantics (an existing camera cut track is returned rather than duplicated) and the fact that the sequence is saved (saved / save_error? in the return). This is real added value; the get-or-create phrasing sits in mild tension with idempotentHint=false, but the differing track_added value between first and later calls makes that defensible rather than contradictory.

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?

Two compact parts, with the purpose front-loaded before the return shape. The Returns block is justified because there is no output schema, so no sentence is wasted; it is only slightly less tidy than a single flowing sentence.

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?

For a single-parameter tool with no output schema, the definition covers purpose, mutation/save behavior, get-or-create semantics, and the exact response fields. An agent has everything needed to call it and interpret the result.

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 100% and the single parameter (sequence_name) is already documented as the target Level Sequence. The description adds no format, naming, or path syntax beyond what the schema supplies, so the baseline 3 applies.

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 definition names a specific verb and resource ('Adds ... camera cut track on a Level Sequence's movie scene'), so the operation and its target are unambiguous. It does not, however, differentiate itself from the closely named siblings add_camera_cut and add_camera_cut_section (track vs. section), leaving that distinction to be inferred.

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?

There is no when-to-use guidance, no prerequisites (e.g. is an open Level Sequence required), and no mention of alternatives such as add_camera_cut or add_camera_cut_section. The parenthetical get-or-create note is behavioral context, not usage routing.

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