xapp_mogrtToPremiere

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

Annotations already establish this is a non-read-only, non-destructive, closed-world write. The description adds real value by disclosing the multi-step behavior (publishes properties, exports a file, places a clip), but omits prerequisites (both apps running, comp open) and whether an existing template file is overwritten.

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?

One dense sentence, front-loaded with the source→destination mapping and ending with the payoff use case; no filler. The em-dash chain makes it slightly harder to parse than a short clause list would be.

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 cross-application orchestration tool with 7 undocumented parameters and no output schema, the description should say what comes back and what happens to the target sequence/track. It covers the flow well but leaves the agent guessing on preconditions and results.

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?

With 0% schema coverage, the description must carry parameter meaning, and it does partially: "chosen AE properties" maps to properties, "text overrides" to texts, and "place it in Premiere" to sequence/track/time. It never explains the layer/property/name structure of the properties array or what templateName does versus compositionName.

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 pipeline (AE properties → Essential Graphics → .mogrt → Premiere) with concrete outputs, so the agent knows exactly what is produced. It does not, however, distinguish itself from near-identical siblings such as xapp_aeCompToPremiere or xapp_toPremiere, which an agent must guess between.

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 trailing phrase "editable titles/lower-thirds in the edit" implies the scenario for using it, but there is no explicit when-not guidance or pointer to the sibling tools that also move AE comps into Premiere. Usage is inferable rather than stated.

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