Delete_Document
Remove a file from SharePoint by specifying its path.
Instructions
Delete a document from SharePoint
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | Yes | Path to the file to delete |
Remove a file from SharePoint by specifying its path.
Delete a document from SharePoint
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | Yes | Path to the file to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It only states 'Delete' without disclosing whether deletion is permanent, if a recycle bin is used, or if specific permissions are required. Safety implications are entirely unspecified.
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 a single sentence with no unnecessary words. However, it could be restructured to front-load critical behavioral details while remaining concise.
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 delete tool with one parameter, the purpose is adequately conveyed, but the lack of behavioral disclosure and guidance makes it incomplete. The missing output schema is acceptable for a delete operation.
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 input schema already describes the file_path parameter with 100% coverage. The description adds no additional meaning beyond what the schema provides, meeting the baseline for complete schema coverage.
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 verb 'Delete' and the resource 'document from SharePoint'. It distinguishes from sibling tools like Delete_Folder, which deletes a folder instead.
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?
No guidance is provided on when to use this tool versus alternatives such as Delete_Folder or when deletion should be avoided. The description does not mention prerequisites, permissions, or conditions for safe use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mdev26/mcp-sharepoint-us'
If you have feedback or need assistance with the MCP directory API, please join our Discord server