lightroom_import_photos

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

No annotations are provided, so the description must fully disclose behavioral traits. The description says 'import' but does not clarify the side effects: does it copy or move files? Does it modify the catalog irreversibly? Does it require user interaction or confirmation? There is no mention of authentication or staging behavior, leaving the agent uncertain about consequences.

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 very short and to the point, but it is under-specified rather than concise. While it is front-loaded with the primary action, it misses critical details. A minimal description for a simple tool could be acceptable, but for a tool with parameters, more context is needed. This earns a 3 because it is not verbose but leaves gaps.

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?

The tool has an output schema (which helps), but the description provides no details on what the import does, how it handles duplicates, error conditions, or supported file types. Given the sibling tools include import_retouched_photo and import_photos, the description does not differentiate them. For a tool that mutates a catalog, this is incomplete.

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%, meaning the parameters (source_path, copy_to, collection_name) are not documented in the schema. The description must compensate by explaining these parameters and how they interact (e.g., what copy_to defaults to, how collection_name is used). It provides no parameter semantics at all, leaving the agent to guess at their meaning and required format.

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 action (import) and resource (photos into Lightroom Classic catalog), which is somewhat distinct from siblings like export_photos. However, it does not specify the source of the photos or the destination beyond catalog, and could be confused with import_retouched_photo. It lacks detail on the import mode (add vs copy vs move).

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 provides no guidance on when to use this tool vs alternatives like import_retouched_photo or export_photos. It does not mention prerequisites, such as whether Lightroom must be running or whether selecting photos is required. An agent would have to infer usage from the name alone.

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