Apply Mogrt Premiere Handoff

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

The annotations already convey non-read-only and non-destructive traits, but the description adds valuable behavioral context beyond them: it targets a 'disposable' verification sequence, imports into an 'empty track,' requires explicit confirmation, and explicitly disclaims any rendered-frame guarantee. It does not elaborate on failure modes or side effects, but the guidance is materially richer than the raw annotations.

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 two sentences with no wasted words. It front-loads the primary action ('Import exactly one previewed MOGRT'), then adds the follow-up read-back and the two critical caveats (explicit confirmation and no rendered-frame claim). Every sentence contributes essential operational 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 return descriptors need not be enumerated. The description covers the target sequence, track state, quantity, confirmation requirement, and a key limitation. It does not explicitly connect to the preceding preview step by name, but the schema's preview_token reference fills that gap. Overall, it is sufficiently complete for a specialized apply step.

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 the parameters preview_token and confirm_import are already fully described in the input schema. The tool description adds no new parameter-specific detail beyond the general mention of 'explicit confirmation,' which aligns with confirm_import. With the schema handling the heavy lifting, a baseline of 3 is appropriate.

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 states a specific verb ('Import'), a specific resource ('exactly one previewed MOGRT'), and a precise destination ('empty track of the explicit disposable Premiere verification sequence'). It also clarifies follow-up action ('read back insertion and control descriptors') and distinguishes this from preview by requiring a 'previewed' MOGRT and explicit confirmation. This is a clear, non-tautological statement of the tool's function.

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 clearly implies this is the apply step after a preview, via 'previewed MOGRT' and the one-time preview_token requirement in the schema. It also states the important precondition of 'explicit confirmation.' However, it does not name sibling alternatives (e.g., preview_mogrt_premiere_handoff or apply_after_effects_render_handoff) or state when not to use this tool, so it falls short of a full routing guide.

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