import_camera_roll

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

With no annotations, the description carries the full burden for behavioral transparency. It discloses that the tool creates folders and imports video files, but lacks details about side effects (e.g., overwriting), required permissions, error handling, or return behavior. The description provides moderate transparency but could be more explicit.

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?

The description is concise and well-structured, with a brief introductory sentence followed by details and a clear Args section. Every sentence contributes useful information without redundancy.

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 moderate complexity (2 parameters, no nested objects, and an output schema exists), the description covers all necessary aspects: folder structure creation, auto-detection logic, and parameter details. The presence of an output schema reduces the need to describe return values.

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?

The description adds significant meaning beyond the input schema, which has no property descriptions. It explains that 'directory' requires an absolute path, and 'camera_letter' is optional with auto-detection based on directory name, including an example. This fully compensates for the 0% schema description coverage.

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 the tool imports a camera roll into an OCF bin structure, creating a specific folder hierarchy. It distinguishes itself from sibling import tools (e.g., import_media, import_audio) by targeting camera roll directories with auto-detection of camera letter.

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 implies usage for camera roll directories and explains the auto-detection feature and optional camera_letter parameter. However, it does not explicitly state when not to use this tool (e.g., for individual files or other import scenarios) or compare it to alternatives.

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