pr_clipOps

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

Annotations cover the safety profile (not read-only, not destructive, not open-world), so the bar is lower. The description adds real context — link/unlink act on the selection, and replaceMedia changes mediaPath on the project item rather than the timeline clip. It doesn't say whether unlink is reversible, what happens to existing links, or whether replaceMedia requires a valid file path.

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?

One dense, front-loaded sentence that enumerates operations without filler. The final 'set name of item' slightly duplicates 'rename', which is minor waste.

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?

With 6 parameters, one enum, and no output schema, the definition should clarify per-action parameter requirements and the scope ambiguity (project item vs timeline clip). It signals a scoping distinction for replaceMedia but leaves other actions' required inputs and return behavior unspecified.

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 only 33%, so the description must compensate, and it partly does by mapping actions to likely parameters (rename→name, colorLabel→label, replaceMedia→mediaPath). But it never names parameters explicitly or explains the 'label' integer semantics (valid range/color mapping) or the clip-object addressing, leaving real gaps.

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?

States a concrete verb domain (clip operations) in Premiere Pro and enumerates the specific operations: select/deselect, link/unlink, rename, color label, replace footage, set item name. An agent can tell it's a multi-action clip mutator. It doesn't distinguish itself from overlapping siblings like pr_setClipProperties or pr_setClipEnabled, which keeps it below a 5.

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?

No guidance on when to use this versus pr_setClipProperties, pr_setClipEnabled, or pr_removeClips, despite clear overlap with setClipProperties for renaming/color. The '(selection)' note for link/unlink hints at a prerequisite, but which action needs which parameters, and when to prefer this tool, is left to inference.

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