Delete SharePoint List Item

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states this is a write operation, that the item may be moved to the site recycle bin, and that delegated Sites.ReadWrite.All is required. This provides valuable context about side effects and permissions beyond the raw schema, though it does not cover every edge case.

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 and front-loaded with the primary action. It includes useful context about permissions and side effects. The Chinese intent line adds length but serves a purpose for multilingual intent matching. Overall it is appropriately sized, though the Chinese portion could be considered optional for a core agent.

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 simple delete operation, the description covers the core aspects: what it does, that it may recycle, and required permission. It does not explain the return value or behavior when the item doesn't exist, but for a straightforward delete tool with no output schema, this is reasonably complete. The lack of annotations raises the bar, and the description meets it adequately.

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 has 100% parameter description coverage, with each of the three parameters (siteId, listId, itemId) clearly described. The tool description adds no additional parameter-specific meaning beyond what the schema already provides. Per the baseline rule for high schema coverage, a score of 3 is appropriate.

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 a specific action ('Delete an item from a SharePoint list') with a distinct resource (list item). This distinguishes it from sibling tools like sharepoint_delete_list and sharepoint_delete_drive_item. The title and description are aligned and unambiguous.

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 clear context (it is for list items, not lists or drives) and notes that it is a write operation. However, it does not explicitly mention when to use this tool versus an alternative, nor does it provide any 'do not use' guidance. The appropriate usage is implied by the resource name rather than explicitly stated.

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