import_mogrt

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool places a template and returns editable properties, but does not disclose permissions, timeline mutation effects, overwrite behavior, or what happens when the target track is occupied.

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 two short sentences with no filler. The core action is front-loaded, and the return-value note is secondary but relevant.

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 mutation tool with no annotations and no output schema, the description is too thin. It mentions returning editable properties but does not explain the return shape, usage context, or parameter details needed to invoke the tool correctly.

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 50%, and the description adds little parameter meaning. It implies that trackIndex selects a video track but does not clarify mogrtPath format, track indexing rules, or the interaction between start and duration.

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 ("Place") and resource ("Motion Graphics template") and specifies the destination ("on a video track"). It is clear what the tool does, but it does not distinguish itself from similar siblings such as place_mogrt_with_media or import_library_graphic.

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 on when to use this tool versus alternatives like place_mogrt_with_media, import_library_graphic, or list_mogrts. It also omits prerequisites, such as whether the template must already be listed or whether a sequence must be active.

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