import_mogrt

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

The description discloses that the tool imports a file and adds it to the timeline, indicating mutation (consistent with readOnlyHint=false). However, it does not elaborate on side effects, error behavior, or whether it creates a new track or replaces existing content. Annotations already indicate non-destructive and non-idempotent behavior, so the description adds minimal value beyond stating the outcome.

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, concise sentence that is front-loaded with key information. It is not verbose, but it could be slightly more structured to include usage context without adding length.

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?

Given 4 parameters and no output schema, the description lacks completeness. It does not explain what happens after import (e.g., does it return a clip reference? an error message?), nor does it provide any prerequisites or file validation details. The agent is left with unanswered questions about the return value and failure modes.

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 100% schema coverage, the baseline is 3. The description does not add any extra meaning to the parameters; it merely states the overall purpose. Parameters like track_index, start_seconds, and duration_seconds are left to the schema's documentation.

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 clearly states the action (Import) and the resource (Motion Graphics Template .mogrt file) and the destination (add it to the timeline). It is specific but does not explicitly differentiate from the sibling tool import_mogrt_from_library, which also imports mogrt files but from a different source.

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?

No guidance is provided on when to use this tool versus alternatives such as import_mogrt_from_library or import_media. There is no mention of prerequisites, file path requirements, or contextual constraints.

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