List SharePoint Library Items

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

With no annotations, the description carries the transparency burden. It discloses the required permission (delegated Files.Read.All) and implies read-only behavior via 'List'. However, it does not mention pagination limits, return format, or behavior for invalid driveId/folderId, which are relevant for an agent. No contradictions with annotations exist.

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 core description is two concise sentences: the action and the permission requirement. The included Chinese intent phrases add length but serve a localization purpose and do not obscure the main statement. It is front-loaded and efficient overall.

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?

The tool is a straightforward list operation, and the description covers what it lists and the permission needed. However, it does not explain what the response contains or how pagination works, and there is no output schema to fill that gap. Given the sibling toolset, this description is adequate but leaves room for edge-case details.

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 all three parameters described in the input schema. The description adds minimal parameter-level insight beyond restating 'root or folder', which is already conveyed by parentItemId's 'Defaults to the library root'. Baseline 3 applies because the schema handles parameter semantics.

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 uses a specific verb ('List') and resource ('files and folders in a SharePoint document library root or folder'), clearly scoping the operation. It distinguishes from siblings like drive_list_root (which targets OneDrive/Drive) and sharepoint_search_drive_items (which is for search) by emphasizing 'SharePoint document library'.

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 implies usage by stating what it lists, and it mentions a prerequisite (delegated Files.Read.All). However, it provides no explicit when-not-to-use guidance or alternatives (e.g., use sharepoint_search_drive_items for searching, or drive_list_children for a user's drive). The context is clear but not directive.

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