copy-drive-item

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

The description adds async behavior (202 Accepted, Location header) beyond annotations. Annotations declare destructiveHint=true and readOnlyHint=false, which align with 'copy' as a write operation. No contradictions. However, it does not detail permissions or conflict resolution.

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 concise (3 sentences) and front-loaded with the action. It includes a tip and example without excessive verbosity. Could be slightly more structured (e.g., bullet points) but is efficient.

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 tool's complexity (nested objects, async) and no output schema, the description covers return format (202, Location header) and use cases. It lacks error handling details but is largely complete for selection and invocation.

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%), and the description adds practical value with an example body structure for parentReference. However, it does not explain childrenOnly and includeAllVersionHistory, which have no schema descriptions. Baseline 3 is appropriate.

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 does 'Asynchronously copy a file or folder to a new location and/or name'. It distinguishes from siblings like move-rename-onedrive-item (move vs copy) and create-onedrive-folder (copy existing vs create new).

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 explicit use cases: 'duplicating templates', 'bulk file provisioning', 'preserving an immutable snapshot'. It implies when to use (copy needed) but does not explicitly state when not to use or compare directly with siblings.

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