Duplicate a collection

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

The description discloses important behavioral details beyond the annotations: the operation snapshots the previous state and supports revert via nuvio_undo. It also clarifies that the copy includes folders and catalog sources and is placed directly after the source, which helps set expectations.

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 two concise sentences with no filler. The core behavior is front-loaded, and the snapshot/revert detail is added only after the primary action.

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?

The description covers the main effect, placement, and undo behavior, but lacks explicit semantics for new_title and profile_id, and there is no output schema. For a mutation tool with four parameters, this is adequate but incomplete.

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 schema provides no field descriptions, and the description only indirectly maps to collection_id and new_id via 'copy a collection' and 'under a new id'. It does not explain new_title or profile_id, leaving 0% schema coverage mostly uncompensated.

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 identifies a specific operation: copying a collection under a new id, including folders and catalog sources. It distinguishes this from simple creation or update by emphasizing duplication and placement after the source.

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 duplication use case is implied by the description, but there is no explicit guidance on when to choose this over nuvio_create_collection or other alternatives. The mention of revert with nuvio_undo is useful but not a direct usage guideline.

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