duplicateCollection

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

Beyond annotations (which only set readOnlyHint=false), the description reveals that the operation is asynchronous by directing to a task status endpoint. It also specifies that duplication is to another workspace, a behavioral constraint not implied by 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 extremely concise with two sentences, no repetitive or unnecessary information. The first sentence states the core purpose, and the second adds a critical note about async status retrieval.

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 complexity (async operation, no output schema), the description lacks explicit mention of the return value (likely a task ID). It also does not cover error conditions or access prerequisites. However, it points to the status endpoint, partially compensating for missing details.

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% and each parameter is already described in the schema. The description adds no additional meaning or context to the parameters beyond what the schema provides.

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 states the tool creates a duplicate of a collection in another workspace, using a specific verb and resource. It distinguishes itself from sibling tools like getDuplicateCollectionTaskStatus by indicating it initiates the duplication process.

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 provides no guidance on when to use this tool instead of alternatives, nor does it mention prerequisites or exclusions. It only points to the task status endpoint for monitoring, which is helpful but not sufficient for usage guidance.

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