import_photos

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Import photos,' which implies a mutating action, but it does not disclose side effects (e.g., copying files, modifying metadata), prerequisites (e.g., Lightroom must be open), or error behavior. This is severely under-informative.

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 a single sentence, which is concise, but it is so under-specified that it is nearly a restatement of the tool name. It is not well-structured to convey necessary information; it is simply too sparse.

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 has 3 parameters (one required), an output schema, and no annotations, the description is completely inadequate. It does not explain the parameters, the behavior, or the return value, leaving an agent without essential context to call it correctly.

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 must compensate by explaining the parameters. It does not mention source_path, copy_to, or collection_name at all. The agent gets no help understanding what these values mean or how they affect the import.

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 states a clear action ('Import photos') and a specific destination ('into Lightroom Classic catalog'), which distinguishes it from sibling tools like export_photos or send_to_photoshop. It is not a tautology, but it lacks any detail about the source or scope.

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 guidance on when to use this tool versus alternatives. It does not mention import_retouched_photo or any other sibling, nor does it state any prerequisites or conditions. The usage is implied only by the tool name.

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