Photos: Copy

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

Adds substantial context beyond the destructiveHint=true annotation: the async timeout behavior, that the operation keeps running server-side after the reply, that a handle is returned for photo_task, and that overwrite replaces existing destination files. These are exactly the behavioral traits an agent needs to reason about a long-running destructive write.

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?

Three tightly packed sentences with no filler; the destructive overwrite behavior is stated at the end and the timeout/handle behavior is front-loaded where an agent will see it before calling.

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?

With no output schema, the description still tells the agent that a handle for photo_task may be returned for long copies, covering the key return-value concern. It leaves some ambiguity about the reply's structure in the synchronous case but is otherwise sufficient for a 6-parameter rewrite tool.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining the on_conflict=overwrite consequence and the same-space/cross-space semantics of space vs dest_space. It does not add syntax or format details for ids/folders/destination beyond what the schema already documents.

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 (copy) and resource (Synology Photos items and/or whole folders), plus the scope of copying into another folder within or across spaces. This clearly distinguishes it from move_photos and copy_files, which act on different resource types or semantics.

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 clear operating context: it blocks up to a task timeout (30 s by default), longer copies continue on the NAS with a handle for photo_task, and on_conflict=overwrite replaces destination files. It does not explicitly name when to prefer move_photos or copy_files, but the copy-vs-move distinction and cross-space capability are clear.

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