Copy SharePoint Library Item

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is asynchronous, which is valuable, but fails to explain what that means for the caller (e.g., how to check progress or what response to expect). It also does not state whether the source item is left unchanged (implied by 'copy' but not explicit) or any permission requirements. This is a significant gap for a mutation tool.

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 the core purpose stated in the first sentence and additional multilingual intents in the second. It is front-loaded and contains no filler. The Chinese intents, while somewhat repetitive, are useful for matching Chinese-language queries and do not detract from clarity.

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 lack of annotations and output schema, the description is incomplete. It does not explain the return value, how the asynchronous operation is tracked, or whether there are any side effects on the source item. The schema covers parameters but not runtime behavior or results. The description should provide more context for an agent to know what to expect.

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 clear descriptions for all four parameters, so the baseline is 3. The description adds no new parameter-level information; it only mentions copying a file/folder, which is already covered by the schema. There is no additional semantics like value ranges or parameter dependencies 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 copies a SharePoint file or folder, with a specific verb ('Copy') and resource ('SharePoint file or folder'), and adds the important distinguishing detail 'asynchronously'. The inclusion of Chinese intents helps clarify the target domain and usage, making it distinct from generic drive copy tools.

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 for copying SharePoint items, but does not explicitly provide alternatives or exclusions. It does not mention when to prefer this tool over similar siblings like drive_copy_item or sharepoint_move_drive_item, leaving the agent to rely on the name and purpose rather than explicit guidance.

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