xapp_aeCompToPremiere

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

Annotations declare a non-read-only, non-destructive operation, and the description adds substantive behavior: the link is live so AE edits propagate, and the open AE project is auto-saved when aepPath is omitted — a side effect worth flagging since destructiveHint is false. It stops short of saying what happens on duplicate comps or whether Premiere needs 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?

Three compact sentences, front-loaded with the core mechanism and the key constraint (no rendering), with the save side effect and optional placement following in priority order. 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?

For a 6-parameter cross-app mutation with no output schema, the description conveys the essential semantics — what it links, where it lands, and the auto-save behavior. It is only incomplete on the bin/sequence parameters and the target sequence requirement.

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 coverage is only 17%, so the description must compensate; it explains aepPath's defaulting behavior and that track/time enable optional placement, which is useful. But bin, sequence, and the units/format of time and track are left entirely undocumented in both schema and description.

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 names a specific verb and resource ('bring After Effects comps into Premiere Pro') and immediately pins down the mechanism ('Dynamic Link', 'live-linked') that distinguishes it from render-based siblings like xapp_renderAEToPremiere. An agent can identify the exact operation without opening the schema.

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?

'WITHOUT rendering' clearly signals the use case and implicitly contrasts with the render sibling, and 'Optionally places the first comp' sets expectations about placement. However, the actual alternative tool (xapp_renderAEToPremiere) is never named, and no prerequisites (Premiere must be open? sequence must exist?) are stated.

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