import_mogrt_from_library

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says 'imports,' while the required sequenceId and time parameters imply the MOGRT is placed onto a timeline at a specific time and track. It does not mention side effects, prerequisites, or failure behavior.

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 a single sentence with no filler, and the key qualifier 'from a Creative Cloud Library' is front-loaded. It is concise, though too sparse to fully carry the behavioral details the operation needs.

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 tool with no annotations and no output schema, this description is incomplete. It fails to explain the placement behavior implied by sequenceId and time, and it gives no context about when the import will succeed or what happens after it runs.

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 schema already documents all six parameters and their roles. The description adds no additional meaning about how the library resolves, where the template lands, or how track indices affect the operation.

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 uses a specific action ('imports') and names the resource ('Motion Graphics Template') and source ('Creative Cloud Library'), which distinguishes it from sibling tools like import_mogrt. It doesn't mention that the template is placed on a sequence, but the core purpose is clear.

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?

There is no guidance about when to use this tool versus alternatives such as import_mogrt, get_mogrt_component, or build_brand_spot_from_mogrt_and_assets. The only hint is 'from a Creative Cloud Library,' which is not enough for an agent to confidently choose between related tools.

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