List OneDrive Folder Items

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

With no annotations, the description carries full behavioral burden, but it only states the action. It does not disclose that it returns immediate children, is a read-only operation, supports pagination via `top`, or what the response structure will be. This leaves the agent to infer core behavior.

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 primary sentence is concise and front-loaded. The Chinese intents line is redundant as a direct translation, but it may serve multilingual intent matching. Overall, the description is compact and efficient, though not maximally so.

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 has no output schema and no annotations, so the description should explain what the response contains or how to use the results. It does not describe return fields, pagination limits beyond the `top` property, or any other context needed to make full use of the tool. This is a significant gap for a listing operation.

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%, so baseline is 3. The description adds little beyond schema: it frames `parentItemId` as 'selected OneDrive folder' but does not clarify `top` or any parameter nuances. It is adequate but not additive to the schema.

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 ('List') and resource ('files and folders under a selected OneDrive folder'), clearly distinguishing it from sibling tools like `drive_list_root`, `drive_list_recent`, and `drive_search_items`. The Chinese intent line reinforces the same 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 provides no explicit guidance on when to use this tool over alternatives, no exclusions, and no prerequisites. It merely implies usage by mentioning 'selected OneDrive folder', but does not describe navigation context or compare with other listing tools.

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