import_retouched_photo

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

No annotations are provided, so the description carries the full burden. It only says the photo is imported and organized into a collection; it does not disclose whether the collection must already exist, whether it is created automatically, whether existing photos are overwritten, or what side effects occur in the Lightroom catalog.

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?

One sentence with no filler, front-loading the main action and immediately stating the organizing effect. Every word earns its place.

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 mutating import tool with no annotations, the description lacks preconditions: the photo must presumably have been sent out for retouching first, and the target collection's existence is unclear. Even with an output schema, an agent may not know how to invoke this correctly without more context.

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 for the parameters. It only loosely maps 'retouched master photo' to file_path and 'collection' to collection_name, but does not explain file path requirements, accepted file types, or collection creation behavior.

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?

States a specific verb ('Import'), resource ('retouched master photo'), destination ('Lightroom Classic'), and additional action ('organize into a collection'). The word 'back' indicates a post-retouching workflow, distinguishing it from generic import_photos and add_to_collection.

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 re-importing a retouched master photo, but does not explicitly state when to choose this tool over siblings like lightroom_import_photos or lightroom_add_to_collection. No alternatives or exclusions are named.

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