Update SharePoint List Item

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

With no annotations, description provides key behavioral context: 'Unspecified fields remain unchanged' clarifies partial-update semantics, and 'Requires delegated Sites.ReadWrite.All' sets auth expectations. Lacks return-value and error behavior details, but the mutation behavior is clear.

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?

Three concise English sentences convey action, key nuance, and permission requirement. Chinese intent lines add multilingual coverage without redundancy. Front-loaded and efficient.

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?

Adequately complete for a simple update tool: says what it updates, how fields behave, and what permission is needed. Missing return-value description and failure modes, but these are not essential for invocation. No output schema increases responsibility, yet the essential information is present.

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% with descriptions for all parameters (siteId/listId/itemId, fields as object keyed by internal column name). Description adds no parameter detail beyond echoing 'selected fields', so baseline 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?

Verb 'Update' + resource 'SharePoint list item' clearly states the action. Distinguishes from sibling tools like sharepoint_update_list (updates a list definition) by targeting list items specifically, and 'selected fields' adds precision.

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?

Implied usage: update an existing list item. No explicit when-to-use vs alternatives, but verb+resource makes the use case self-evident. Permission requirement is a prerequisite rather than usage guidance.

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