import_media

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

The description reveals the batch-then-fallback behavior, which is useful, but does not disclose potential side effects (e.g., overwriting, permission requirements, error handling). With no annotations, more detail would be beneficial.

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?

Three short sentences, no extraneous information. Efficiently conveys the core purpose, strategy, and parameter meaning.

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 the tool's simplicity (1 parameter, has output schema), the description is mostly complete. It covers the essential behavior and parameter, though it could mention failure modes or state dependencies.

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 0%, so the description adds value by specifying 'absolute file paths'. This clarifies what the parameter expects beyond the schema's bare type definition.

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 it imports media files into the current media pool folder, distinguishing it from siblings like 'import_audio', 'import_camera_roll', and 'import_media_to_bin' which have more specific targets.

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 explicit guidance on when to use this tool versus alternatives. The description mentions the batch/fallback strategy but does not provide context for selecting this over other import tools.

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