Apply Mogrt Premiere Handoff

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

Annotations already declare the non-read-only, non-idempotent, non-destructive, closed-world profile. The description adds genuinely useful context beyond that: it is bounded to a disposable verification sequence, it requires explicit confirmation, and it makes 'no rendered-frame claim', clarifying that only insertion and control descriptors are verified.

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?

Two sentences, front-loaded with the action and scope, with no wasted clauses. The jargon ('explicit disposable Premiere verification sequence') is dense but each phrase carries scope information.

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?

An output schema exists, so the read-back of insertion and control descriptors need not be detailed. For a bounded, confirmation-gated mutation the description covers scope, precondition, and limits well.

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 100%, so preview_token and confirm_import are already documented in the schema. The description reinforces 'exactly one' and the confirmation requirement but adds no new syntax or format detail beyond what the schema provides, making 3 the correct baseline.

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 specific verb (import), a precise resource (exactly one previewed MOGRT), and the exact destination (empty track of the disposable Premiere verification sequence). This clearly distinguishes it from the sibling preview_mogrt_premiere_handoff, which produces the preview rather than consuming it.

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 description implies the tool must be preceded by preview_mogrt_premiere_handoff ('previewed MOGRT') and states the confirmation requirement. It does not spell out explicit when-not conditions, but the preconditions are clear.

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