copy-drive-item

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

The description states it is a non-destructive copy operation, but annotations declare destructiveHint=true, creating a direct contradiction. Per rubric, score is 1 when description contradicts 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 well-structured with a clear purpose first, followed by an example and use cases. It is relatively concise (~80 words) but includes minor fluff like '💡 TIP:'. Front-loading is effective.

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 no output schema, the description explains the async return (202 Accepted with Location header) and use cases. It covers key behavioral aspects but lacks guidance on when to use copy vs. move and does not describe all parameters in detail.

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 high (80%), baseline 3. The description adds value by providing a concrete body example with parentReference and name, clarifying usage beyond the schema. However, it omits details on parameters like childrenOnly and includeAllVersionHistory.

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 'Asynchronously copy a file or folder to a new location and/or name,' providing a specific verb (copy) and resource (file/folder). It distinguishes from siblings like 'move-rename-onedrive-item' by emphasizing duplication rather than relocation.

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 explicit use cases ('Ideal for duplicating templates, bulk file provisioning, preserving an immutable snapshot'), giving clear context for when to use. However, it does not explicitly mention alternatives or when not to use, such as preferring a move operation.

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