Delete_Document

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

No annotations are provided, so the description must carry full burden. It mentions 'Permanently delete', implying irreversibility, but does not disclose permissions needed, side effects (e.g., on version history), or behavior when the file does not exist. This is minimal disclosure for a deletion 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?

Two concise sentences, front-loaded with the key action and a helpful usage hint. No unnecessary words or redundancies.

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 deletion tool with an output schema (not shown but indicated), the description covers the core purpose and a special case. However, it lacks details on file_name parameter semantics and error handling behavior, leaving room for ambiguity.

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 must compensate. It only adds meaning for folder_name (empty string for root), but provides no guidance on file_name (e.g., format, extension, path). Given no param descriptions in schema, the description is insufficient to help the agent understand all parameters.

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 action ('Permanently delete') and the resource ('document from a SharePoint folder'), and distinguishes from sibling tools (e.g., Delete_Folder) by specifying 'document'. It also provides a specific usage hint for files in the document library root.

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 gives a specific tip for using empty string folder_name for root files, but does not explicitly state when to use this tool versus alternatives like Delete_Folder or other sibling tools. The context signals show many related tools, but no explicit when-not-to-use guidance is provided.

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