import_media

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

No annotations provided, so description carries full burden. It only states basic function, omitting behaviors like error handling, overwride behavior, idempotency, or whether it modifies media pool state beyond adding. Minimal behavioral disclosure.

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?

Single sentence, front-loaded with key information, no wasted words. Highly efficient.

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?

Provides essential context (absolute paths, current folder) but lacks input validation, error conditions, success feedback, and potential side effects. With no output schema and no sibling differentiation, more detail would help agent decision-making.

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?

Input schema has 0% description coverage. Description adds meaning: paths must be absolute and on the Resolve machine. However, it doesn't specify format constraints, path separator expectations, or behavior for multiple paths. Partially compensates but leaves gaps.

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?

Description clearly states the verb 'import', resource 'media files', and context 'absolute paths on the Resolve machine' and 'current media pool folder'. It distinguishes from siblings like list_media (listing) and import_timeline (different resource).

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?

Implies usage for importing media from absolute paths, but no explicit guidance on when to use vs alternatives like import_timeline or when not to use. Lacks conditions like file type support or path validation.

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