trim_clip

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

The description discloses refusal behaviors (retimed clips, keyframe issues) and mentions verification of the timeline edge, going beyond the annotations. It doesn't detail side effects or return values, but the refusal logic is clearly stated.

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 concise and well-structured: it states the action, then conditions and defaults. No unnecessary fluff, each sentence adds value.

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?

The description covers the main purpose and constraints, but doesn't mention return values or errors explicitly. Given there's no output schema, it could be more complete, but it is sufficient for understanding usage.

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 description adds the 'exactly one' constraint for new_in_seconds and new_out_seconds, which is not enforced in the schema. It also provides context for the keyframe_policy parameter by explaining the default refusal behavior. Overall, it supplements the schema descriptions.

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 states the tool's primary function: trimming exactly one source in/out point. It distinguishes from related operations like moving or splitting clips by specifying the exact action and the constraints (refuses retimed clips, handles keyframes).

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 usage constraints: trim exactly one edit point, refuses retimed clips, and by default refuses trims that leave keyframes outside the visible clip. It doesn't explicitly compare with alternatives but implies when to use by stating these conditions.

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