Read SharePoint List Changes

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

No annotations are provided, so the description carries the burden. It adds valuable behavioral information by stating the tool returns 'nextLink or deltaLink state', implying pagination and delta continuation support. However, it does not disclose details such as whether deleted items include metadata, how tokens should be handled, or any authentication requirements, leaving gaps in transparency.

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, with two sentences that front-load the core purpose and include useful Chinese translations for bilingual support. Every sentence adds value without unnecessary repetition or filler.

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 absence of an output schema and annotations, the description provides a reasonable high-level overview but lacks critical details such as the response format, how to initiate a fresh delta link, and how to use returned tokens for pagination. This is a moderately complex delta operation, and the description could better explain the token lifecycle and item response structure.

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 provides 100% coverage with descriptions for all four parameters, so the baseline is 3. The description does not add additional meaning beyond the schema; it mentions nextLink/deltaLink state but does not elaborate on how the 'token' parameter works, which the schema already partially covers.

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 'Read newly created, updated, or deleted SharePoint list items' with a specific verb and resource, and distinguishes itself from sibling tools like sharepoint_list_list_items by focusing on changes and delta state. The mention of returning 'nextLink or deltaLink state' further clarifies its unique 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 communicates when to use this tool by indicating it handles changes (newly created, updated, deleted) and includes Chinese intents '增量同步清单' (incremental sync) and '获取列表Delta' (get list delta), which imply synchronization scenarios. It does not explicitly state when not to use it or name alternatives, but the context is clear and sufficient for selection.

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