import_media

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

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: it verifies the imported items appear in the project. However, it omits permission requirements, duplicate/overwrite handling, failure behavior, and the fact that it mutates project state.

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 naming the action, the input, the destination, and the verification step with no filler. Every clause earns its place.

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?

No output schema or annotations exist, so the description should do more for a state-mutating 4-parameter tool. The verification clause helps, but permissions, error conditions, and duplicate handling are absent, leaving meaningful gaps.

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 four parameters are already well documented, establishing a baseline of 3. The description's mention of 'video, audio, or image files' loosely connects to import_as_numbered_stills but adds no syntax or format detail beyond 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 ('Import') and resource ('local video, audio, or image files') with the target ('Premiere Pro 2019 project'). It is the only import tool among the siblings, and its function is immediately distinguishable from readers like list_project_items or search_project_media.

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?

The description gives no when-to-use guidance, no prerequisites (e.g. an open project/running Premiere instance), and no contrast with alternatives such as search_project_media or place_media_on_timeline. An agent must infer the correct invocation context entirely.

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