Apply After Effects Render Handoff

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

Adds meaningful behavior beyond the annotations (readOnly=false, idempotent=false, destructive=false, openWorld=false): a confirmation is required, both hosts and file metadata are rechecked, and the token is consumed before dispatch, implying one-time non-repeatable semantics. It also enumerates what is not touched. It stops short of describing failure behavior if the token is expired or already consumed.

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?

Three tight sentences; the operative action and its scope constraint are front-loaded, and each remaining sentence adds a distinct constraint (confirmation, token consumption, exclusions). No filler.

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 values need not be explained. For a two-parameter, non-destructive apply operation the description covers preconditions, side effects, and exclusions well; only edge-case failure handling is left implicit.

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% and both parameters (preview_token, confirm_import) are documented in the schema, so the baseline is 3. The description reinforces 'requires confirmation' and the one-time token nature but adds no syntax, format, or constraint detail beyond what the schema already provides.

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 and resource: import exactly one previewed completed AE render into its approved Premiere bin. The phrase 'exactly one' plus 'previewed completed' distinguishes it from preview_after_effects_render_handoff, preview_after_effects_render, and enqueue_after_effects_render at a glance.

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?

Gives clear context: the render must be 'previewed completed' and already have an 'approved' bin, and it states the negative scope ('Does not save, render, or change a timeline'). It does not explicitly name preview_after_effects_render_handoff as the mandatory prerequisite (the schema does), nor contrast with the sibling apply_mogrt_premiere_handoff.

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