lightroom_add_to_collection

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

There are no annotations, so the description bears the full burden of behavioral disclosure. It only states the basic add operation and does not clarify whether adding duplicates is allowed, whether the collection is modified in place, what happens on invalid IDs, or whether any destructive behavior is possible.

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 seven-word sentence with no filler. It is front-loaded with the action and object, making it immediately scannable.

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 mutation tool with no annotations and no schema parameter documentation, the description is too thin. It lacks prerequisites, failure behavior, and any connection to sibling tools that supply the required IDs. The presence of an output schema reduces the need to document return values, but the invocation context remains underspecified.

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%, and the description only loosely maps 'photos' to photo_ids and 'existing collection' to collection_id. It does not explain acceptable ID formats, where to obtain valid photo IDs, or how collection_id relates to collection listing tools.

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 and object: 'Add photos to an existing collection.' It effectively distinguishes itself from collection creation tools. However, it does not differentiate from the sibling 'add_to_collection', which appears to be the same operation.

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?

No guidance is given about when to use this tool versus alternatives. It does not mention that photos should already exist in Lightroom, that the collection must already exist, or that photo IDs might come from get_selected_photos. The agent is left to infer the appropriate invocation context.

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