pr_trimClip

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows it is a non-destructive write. The description adds the mode distinction but does not say whether trimmed material is recoverable, how linked audio behaves, or what happens if both timeline and source points are supplied.

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?

A single front-loaded sentence with no filler, product name first and the operative detail immediately after. It is arguably over-compressed for a 6-parameter nested tool, but nothing in it is wasted.

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 mutation tool with a nested clip selector, 6 parameters and no output schema, the description covers the core intent but omits interaction rules between the timeline and source parameters and any confirmation of what the call returns. Adequate minimum, but gaps remain.

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 67% and the description only restates what the schema already documents (start/end in seconds, inPoint/outPoint). It adds no unit or format information for inPoint/outPoint, which are the two undocumented params, so those remain ambiguous.

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?

Names a specific verb and resource ('trim a timeline clip') in the Premiere Pro namespace, and lists the two trim modes (timeline start/end vs source inPoint/outPoint). It is distinguishable from siblings like pr_razor or pr_moveClip, though it does not explicitly contrast with them.

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 'and/or' phrasing implies you may trim timeline extents, source extents, or both, which is mild usage guidance. There is no statement on when to prefer this over pr_setInOut, pr_removeRange, or pr_moveClip, and no mention of prerequisites such as an open sequence.

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