import_media

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

With no annotations provided, the full burden of behavioral disclosure falls on the description, and it only partially delivers. It confirms the operation is an import into the current project and enumerates supported types, but it doesn't state what happens on duplicate imports, whether bins are auto-created, what happens if the file doesn't exist, what is returned, or what prerequisites exist. For a file-system-mutating operation, these are meaningful omissions.

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 front-loaded sentence with the verb 'Imports' leading, followed by the object and destination. The '(video, audio, image)' parenthetical is efficient scope clarification with zero wasted words. Every element earns its place and the structure mirrors good writing practice — no fluff, no redundancy with the schema.

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 2-parameter tool with full schema coverage and no output schema, the description plus schema covers the what and where adequately — the schema documents both parameters well, and the description closes the question of scope and types. However, no annotations exist to cover behavioral risk, and the description is silent on error conditions, return values, and preconditions. It's the minimum viable description for a tool of this complexity.

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 baseline is correctly 3; both filePath (absolute path) and binName (bin or root) carry complete JSON Schema descriptions. The description text adds no parameter-level meaning beyond the schema — it doesn't even hint that binName controls bin targeting — but since the schema is fully self-sufficient, the description's silence causes no information loss.

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 verb 'imports' with a concrete resource 'a media file (video, audio, image)' and a destination scope ('into the current Premiere Pro project'), which is clear and well-scoped. However, differentiation from the massive sibling list of import_* tools (import_folder, import_sequences, import_mogrt, import_fcp_xml, import_edl, import_image_sequence) is only implicit via the file-type parenthetical; no explicit sibling is named for disambiguation, so it stops short of a 5.

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 the many overlapping alternatives in the import_* family or when not to use it. There are no exclusions, no alternative tool names, and no mentions of prerequisites such as an open project, despite 'current' implying one is needed. The agent is given no framework for selecting among import_media, import_folder, import_sequences, import_image_sequence, or import_mogrt.

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