overwrite_clip

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It reveals nothing about side effects, required permissions, undo behavior, track targeting, or what happens to the source and destination. The agent has no insight into the operation's impact.

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 under-specified rather than concisely detailed. It is a single vague phrase that lacks any structure, benefits, examples, or clear action. It does not front-load useful information; it merely restates the name.

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 the absence of annotations and output schema, the description is the sole source of context. It is grossly insufficient for a mutating operation that clearly affects the timeline. It provides no information about behavior, edge cases, or expected results, making it nearly useless for an agent deciding to invoke it.

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 tool has zero defined parameters and the schema is effectively empty (only additionalProperties allows arbitrary properties). Since there are no parameters to explain, the baseline is 4. The description does not add or subtract from this, though it also gives no hint of implicit inputs that might be expected.

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 'Premiere Pro expanded operation: overwrite clip' merely restates the tool name with a generic 'expanded operation' prefix. It fails to specify what overwrite clip does in Premiere Pro, such as replacing a clip on the timeline without affecting other tracks, or distinguishing it from related tools like overwrite_from_source.

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?

There is no guidance on when to use this tool versus alternatives. The phrase 'expanded operation' is vague and does not explain the intended context, prerequisites, or conditions for invocation. No comparisons to sibling tools or exclusion criteria are provided.

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