lightroom_import_retouched_photo

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states the action and collection organization, without revealing side effects such as whether the collection is created if missing, whether duplicates are created, or whether existing photos are overwritten. A mutation tool like this should provide more transparency.

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?

A single, front-loaded sentence that wastes no words. It communicates the core action and the organizational side-effect efficiently.

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?

For a simple two-parameter import tool with an output schema, the description covers the basic purpose. However, it omits guidance about collection existence, the relationship to send_to_photoshop, and any prerequisites like Lightroom Classic being open, leaving some gaps for an agent to infer.

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. It adds meaning by clarifying that file_path refers to a retouched master photo and that the result is organized into a collection, which maps to collection_name. However, it does not explain the default collection value, required path format, or how the collection is chosen.

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 verb 'Import' and the resource 'retouched master photo back into Lightroom Classic,' plus the organizing action into a collection. This distinguishes it from generic import_photos and the outgoing send_to_photoshop workflow.

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 phrase 'retouched master photo back' implies the tool is for re-importing an externally edited file, which gives some context but does not explicitly name alternatives or when not to use it. No clear comparison to import_photos, add_to_collection, or create_collection is provided.

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