import_media

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

With no annotations, the description carries the full behavioral disclosure burden. It only says media is imported into the current Premiere Pro project; it does not mention prerequisites like an open project, error conditions, whether bins are created, or any effects on existing project items. Minimal behavioral context is provided.

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?

A single, compact sentence with no filler. The core verb, resource, media scope, and target destination are all present, and the sentence is front-loaded with the action.

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 simple two-parameter tool with fully described parameters, the baseline completeness is acceptable. However, there is no output schema, no annotations, and many import-related siblings, so the sparse description leaves gaps around return/error behavior, single-file-only semantics, and when to use a different import tool.

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% and both parameters already have clear schema descriptions, including the default bin behavior. The tool description adds no parameter-level meaning beyond 'media file', so it does not compensate or extend the schema.

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?

States a specific verb and resource: 'Imports a media file (video, audio, image) into the current Premiere Pro project.' The media type parenthetical adds useful scope, and the description is clearly about a single file import. It does not explicitly contrast with sibling tools like import_folder, import_image_sequence, or import_sequences, so it is clear but not fully differentiated.

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 given about when to choose import_media versus the many import-related siblings. There is no mention of alternatives, exclusions, or conditions such as a single file versus folder or sequence import, so the agent must infer usage purely from the name and schema.

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