pr_createSequence

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

Annotations already disclose that this is a non-read-only, non-destructive, closed-world creation operation. The description adds useful non-obvious behavior about settings derivation from clips and how width/height/fps are applied, but it does not cover side effects such as name collisions, bin handling, or what is returned or opened after creation.

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 a single front-loaded sentence with a useful parenthetical example (3840x2160 @ 25). Every clause contributes information about a creation mode or setting derivation.

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 seven parameters, low schema description coverage, and no output schema, the description covers the core creation modes but is incomplete on bin/name semantics, mode precedence, and result behavior. It is adequate but leaves meaningful gaps for an agent invoking the tool.

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 description coverage is only 14%, so the description must compensate. It explains clips, presetPath, and width/height/fps semantics reasonably well, but it leaves bin and name behavior undocumented and does not clarify how conflicting mode parameters are resolved.

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 gives a specific verb and resource — create a Premiere Pro sequence — and enumerates three concrete creation modes (clips, .sqpreset, default preset plus dimensions/fps). It is very clear what the tool does, but it does not explicitly distinguish itself from nearby sequence-related siblings such as pr_duplicateSequence or pr_openSequence.

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 three modes imply when each input path should be used: clips derive settings from the first clip, presetPath uses a .sqpreset, and width/height/fps apply after a default preset. It does not state when to prefer this tool over pr_duplicateSequence or pr_openSequence, so it falls short of fully explicit alternative guidance.

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