scene_edit_detection

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

With no annotations, the description must disclose effects, return behavior, or prerequisites, and it does none of these. It does not say whether scene edit detection creates markers, returns a list of edits, opens a dialog, or requires an open sequence.

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 text is short, but brevity is under-specification rather than conciseness because the only content repeats the name. The 'expanded operation' prefix adds context about the product but no actionable guidance.

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?

There is no output schema and no return-value description, so an agent cannot know what this call returns. The definition is also incomplete because it fails to explain the relationship to detect_scene_edits or what side effects the operation has on the project.

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 declared parameters, so no parameter documentation is required; the baseline for 0 params is 4. The schema's additionalProperties:true is odd but does not create a documented parameter obligation.

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: scene edit detection' essentially restates the tool name without a verb or observable action. It gives no way to distinguish this tool from the sibling detect_scene_edits, which appears to describe the same operation.

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 statement about when to call this tool or when to prefer detect_scene_edits instead. The sibling list strongly suggests a near-duplicate exists, but the description provides no selection criteria.

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