razor_timeline_at_time

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

No annotations are present, so the description carries the transparency burden. It clearly discloses that the tool cuts across multiple tracks and defaults to all tracks if no arrays are given, but does not mention undo behavior, locked tracks, or potential error cases.

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 concise sentences front-load the core action and the critical default behavior. Every word earns its place with no redundant content.

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 a well-documented schema and a straightforward operation, the description adequately covers the core behavior and defaults. It lacks return value and error handling, but for a mutating cut command that is acceptable; could mention undo or prerequisite sequence state.

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 already documents all four parameters with individual descriptions, so the description adds limited new semantic value. The line about no track arrays defaulting to all tracks complements but mainly restates what the schema already implies per-parameter.

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 a specific verb ('Cuts') and resource ('multiple tracks in a sequence') with a precise condition ('at an absolute timeline time'). It differentiates from siblings like razor_all_tracks by noting optional track arrays and the default to all tracks.

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 provides context about default behavior when track arrays are omitted, but does not explicitly compare with alternatives like razor_all_tracks or split_clip. Usage is implied rather than directly stated as 'use this when...'.

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