List SharePoint Document Libraries

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

With no annotations, the description carries the burden; it discloses the delegated permission requirement and the drive-return mapping. It does not detail pagination or error behavior, but for a simple list operation these gaps are minor.

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 short and front-loaded, with only two English sentences plus a Chinese intent hint. The Chinese phrase set adds minor redundancy but is compact and serves multilingual matching.

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 straightforward read/list tool, the description plus the full parameter schema covers the operation scope, auth requirement, and return model. The absence of an output schema is mitigated by the explicit 'returned as a drive' statement, though it doesn't describe response envelopes or failures.

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%, and the input schema already documents siteId and top. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline 3 applies.

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 specifies the exact action ('List'), the resource ('document libraries available in a SharePoint site'), and clarifies that each library is represented as a drive, which helps distinguish it from sibling SharePoint list tools.

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?

It provides clear operation context and a required permission ('Requires delegated Files.Read.All'), but it does not explicitly contrast with alternative tools such as sharepoint_list_lists or state when not to use it.

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