copy_develop_settings

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

With no annotations, the description carries the full burden. It states that all Develop adjustments are copied but does not disclose that target settings will be overwritten or replaced, whether the operation is reversible, or any prerequisites. 'Sync' hints at mutation but leaves the destructive effect unstated.

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; every word contributes scope and direction. The key qualifier 'all' is front-loaded and immediately signals that this is a full-copy operation.

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 simple 2-parameter shape and the presence of an output schema, the core invocation is clear. However, the absence of any caveat about overwriting existing target adjustments and the lack of usage guidance leave the description incomplete for an agent deciding whether the tool is safe and appropriate.

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?

The description maps source_photo_id to the photo providing adjustments and target_photo_ids to the receiving photos, and clarifies multiplicity via 'multiple target photos.' Schema description coverage is 0%, so this mapping is the only semantic cue; it does not detail acceptable ID forms or how IDs relate to other Lightroom entities.

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 the action ('Sync'), the resource ('Develop adjustments'), and the direction (source photo to multiple target photos). This clearly distinguishes it from set_develop_settings or apply_develop_preset, which do not imply copying from another photo.

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 a bulk-copy use case but never names alternatives or exclusions. An agent must infer that this is for copying all adjustments from one photo rather than setting specific settings, so the when-to-use guidance is only implicit.

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