list-site-list-items

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that returned items include field values, which is mildly useful, but does not disclose pagination behavior, truncation, or that cursor ignores other query inputs. With the annotations in place, a neutral score is appropriate.

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 a single, front-loaded sentence with no filler or redundancy. Every word contributes to meaning, and it is immediately clear what the tool returns.

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 read-only list operation with no output schema, the description plus the rich parameter schema is largely sufficient. It covers the core return value ('items with field values'), and the schema handles pagination and filtering details. It could be slightly more complete by mentioning the relationship to get-site-list-item, but nothing critical is missing.

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 description coverage is 100%, so the schema fully documents all five parameters, including cursor, filter, maxItems, siteId, and listId. The description adds no parameter-level meaning beyond the schema. Baseline 3 is correct because the schema carries the explanatory burden and does so adequately.

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 states a specific verb-resource pair, 'List items of a SharePoint list', and adds 'including their field values' to indicate the data returned. It is distinguishable from siblings like get-site-list-item by the plural 'items' and from list-site-lists by the focus on item-level listing. However, it does not explicitly contrast itself with the singular get-site-list-item or mention scope like 'all items'.

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 guidance on when to choose this tool over alternatives such as get-site-list-item or list-site-lists. There is no mention of prerequisites, use cases, or exclusions. The usage context is only implied by the tool's name and plural 'items'.

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