xapp_renderAEToPremiere

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

Annotations already declare it is not read-only, not destructive, and closed-world. The description adds genuinely useful behavior: the render is blocking via the AE render queue, and it can emit specific formats/codecs. It omits whether an existing file at outputPath is overwritten and what side effects occur in the Premiere project.

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?

It is a single front-loaded sentence that packs the action, the method, and the rationale with no filler. The parenthetical format list is dense but earns its place by illustrating the output module.

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 7-parameter, cross-application, blocking operation with no schema descriptions and no output schema, the description leaves too much unexplained: there is no mention of where the file lands by default, how sequence/bin/track placement is decided, or what the caller gets back on completion.

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 0% for 7 parameters, so the description carries the full burden, yet it only hints at outputModuleTemplate through format examples (ProRes 4444, High Quality with Alpha, H.264). It says nothing about compositionName, outputPath, bin, sequence, track, or time.

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 chain ("Render an After Effects comp to a file ... and import + place the result in Premiere") and names the resource and destination app. It also implicitly separates itself from the Dynamic Link path used by siblings like xapp_aeCompToPremiere.

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?

It gives a concrete selection condition: use this "when Dynamic Link playback is too heavy." That is clear context for when to pick it over the Dynamic Link route, though it never names that alternative tool explicitly or states exclusions.

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