Duplicate Collection

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

Annotations already convey that this is a mutating, non-idempotent, non-destructive operation, but the description adds no additional behavioral context. It does not disclose whether a new collection is created, whether documents and members are copied, or whether duplicate operations are asynchronous or require special permissions. No contradiction exists, but the description does not go beyond the structured annotations.

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, front-loaded sentence with no redundant wording. It states the action and target resource directly, making the tool easy to scan and understand.

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 one-parameter tool with 100% schema coverage and relevant annotations, the description is minimally viable. However, it leaves some ambiguity about whether collId refers to the source collection only, what the output is (e.g., a new collection ID), and whether duplication is asynchronous or blocks until complete.

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 100% coverage with a clear 'Collection ID' description for collId, so the baseline is 3. The tool description does not add parameter-level details, but the single parameter is already well-documented by the schema.

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 uses the specific verb 'Duplicate' with the resource 'an entire collection', which clearly states what the tool does. It also distinguishes itself from the sibling transkribus_coll_duplicate_doc by indicating this operates at the collection level rather than document level.

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 offers no guidance on when to use this tool versus alternatives like transkribus_coll_create, transkribus_coll_export, or transkribus_coll_duplicate_doc. It also does not mention any prerequisites, naming behavior, or cases where this tool should be avoided.

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