Delete SharePoint List

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose 'Requires delegated Sites.Manage.All', which is useful authorization context. However, it does not state that deletion is irreversible or that all items in the list are also removed, which is critical for a destructive operation.

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 core action and permission, and includes compact multilingual intents. It avoids redundancy and every part serves a purpose for agent understanding.

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 destructive delete operation, the description lacks critical context: no warning about permanent data loss, no mention of cascading deletion of list items, and no post-conditions or confirmation of what happens after execution. While it covers permissions and scope, it is incomplete for safe use.

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?

Both parameters (siteId and listId) are fully described in the input schema, providing 100% schema coverage. The description adds no additional parameter-level semantics, such as how to obtain the IDs or any constraints, so it stays at the baseline of 3.

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 'Delete an entire SharePoint list', providing a specific verb ('delete') and resource ('entire list'). The word 'entire' distinguishes it from item-level deletion tools like sharepoint_delete_list_item, and the Chinese intents reinforce the purpose.

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 no explicit guidance on when to use this tool versus alternatives such as sharepoint_delete_list_item or sharepoint_delete_drive_item. It only mentions the permission requirement (Sites.Manage.All) but does not provide usage context, exclusions, or alternative tool references.

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