Copy File

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

Annotations already flag it as non-read-only, non-destructive, non-idempotent, and open-world. The description adds valuable context: the operation is asynchronous and may take time for large files, and it requires user confirmation. No contradictions.

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 with a clear structure: purpose sentence, then Args, Returns, Raises sections. The emoji and 'recommended' comment are slightly informal but do not add unnecessary length. Every sentence contributes value, though some details could be condensed.

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 presence of an output schema and sibling tools, the description covers purpose, async behavior, parameters, returns, and errors. Missing details include default naming behavior when new_name is omitted and permission requirements, but overall it's fairly 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?

Schema description coverage is 0%, so the description carries the burden. It provides brief explanations for each parameter (e.g., 'file_id: The file ID to copy'), but lacks details on formats, sources, or constraints (e.g., where to find account_id, naming rules for new_name). This is minimal but sufficient for basic use.

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 'Copy a file within OneDrive', specifying the verb 'copy' and resource 'file'. It distinguishes from sibling tools like file_move (which moves instead of copies) and file_create (which creates a new empty file).

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 implies usage via 'copy a file' and notes it's asynchronous, but does not explicitly state when to use this tool versus alternatives like file_move or file_rename. It mentions 'requires user confirmation recommended' but lacks prerequisites or exclusions.

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