trim_clip

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

No annotations are provided, so the description must fully disclose behavior. It only states that in/out points are changed in seconds, but does not reveal potential side effects (e.g., clipping beyond source duration), whether parameters are optional, or the effect of omitting inSeconds/outSeconds.

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 sentence that conveys the core action and unit without extraneous words. It is well-structured for quick comprehension.

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 6 parameters (3 required) and no output schema, the description is too sparse. It does not explain how parameters interact, valid ranges, or whether inputs are relative or absolute. An agent needs more detail to use the tool 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?

Schema description coverage is only 17% (only trackType has a description). The description adds no meaning for the parameters; it mentions 'in/out points' but does not map them to 'inSeconds' or 'outSeconds', nor explain 'clipIndex', 'trackIndex', or 'sequenceName'. It fails to compensate for the low coverage.

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 specifies the action ('trim head/tail'), the resource ('timeline clip'), and the unit ('seconds of source media time'). It effectively distinguishes from sibling tools like 'move_clip' or 'remove_clip' by focusing on in/out point modification.

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 no guidance on when to use this tool versus alternatives, such as 'move_clip' or 'apply_effect'. It lacks context about prerequisites or scenarios where trimming is appropriate.

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