List SharePoint List Items

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

With no annotations provided, the description must disclose behavioral traits itself. It does include a required permission ('Requires delegated Sites.Read.All') and a performance hint about filters, which adds value. However, it omits details about pagination, default page size, sorting, or what happens when fieldNames is omitted—gaps that are not covered by the schema's brief field descriptions.

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 front-loaded with the primary purpose and remains concise. The Chinese intent list adds lengthy synonym phrases, which may be useful for multilingual queries but is somewhat redundant for an AI agent. The overall structure is clear and the essential information is presented early.

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 tool with 5 parameters and no output schema, the description is adequate but not thorough. It covers the core action and a permission requirement, but does not explain pagination behavior, the default return size, or the effect of fieldNames on the response. These gaps are partially mitigated by the schema's field descriptions, but the description itself could be more complete given the absence of annotations.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description's filter tip ('Optional filters work best on indexed columns') is already echoed in the schema's filter description ('Prefer indexed columns'), so it adds no new parameter semantics. No other parameter guidance is provided in the description, leaving it at baseline.

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 begins with a clear verb and resource: 'List items and field values in a SharePoint list.' This distinguishes it from sibling tools like sharepoint_get_list_item (singular item) and sharepoint_list_item_delta (incremental changes). The Chinese intents reinforce the purpose without ambiguity.

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 provides an implied usage context—listing SharePoint list items—and a practical tip about filters on indexed columns. However, it does not explicitly state when to use this tool over alternatives like get_list_item or list_item_delta, nor does it mention any exclusions or prerequisites beyond the permission note.

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