Delete 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 a write, may move the item to the recycle bin, and requires delegated Files.ReadWrite.All. This provides meaningful behavioral context beyond the schema, though it does not detail error outcomes or folder deletion semantics. Still, it is substantially transparent.

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, front-loaded with the primary action, and each sentence adds value. The Chinese intent list is a practical convenience without bloating the description. No waste.

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?

For a simple two-parameter deletion tool with no output schema, the description covers purpose, behavior, auth, and localization. It omits potential error details or effects on folder contents, but these are not critical for basic usage. The information provided is sufficient for an agent to select and invoke the tool correctly.

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 both parameters (itemId, driveId) have descriptive explanations in the schema. The description itself adds no additional parameter guidance, so it relies on the schema. Baseline 3 is appropriate because the schema handles parameter semantics adequately.

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 deletes a file or folder from a SharePoint document library, with a specific verb and resource. It distinguishes itself from sibling tools like sharepoint_delete_list_item and drive_delete_item by explicitly mentioning SharePoint library and file/folder scope. Chinese intent examples reinforce clarity.

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 clear context: it is a write operation for SharePoint library items and notes the required permission (Files.ReadWrite.All). It does not explicitly mention alternatives or exclusions, but the SharePoint library focus and permission requirement effectively guide usage. No explicit 'use this instead of' guidance, but the context is sufficiently clear.

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