list-my-drive-folder-items

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds a useful scoping clue—items must be inside a specific OneDrive folder—but does not disclose pagination/truncation behavior or the continuation semantics that the maxItems parameter description hints at. It is not misleading, but it adds limited behavioral context beyond annotations.

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?

A single clear sentence with no wasted words. The action and resource are front-loaded, making the description easy to scan and understand.

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 input schema and annotations are rich, covering all parameters and the read-only/idempotent nature of the call. Still, the description alone leaves out important context: no mention of direct-child semantics, pagination behavior, or how this tool relates to nearby siblings. It is adequate for basic invocation but not fully complete.

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 the parameter descriptions already handle cursor, filter, select, orderby, and maxItems. The tool description adds value by clarifying that the required itemId refers to a OneDrive folder rather than an arbitrary item, which is meaningful because the schema's itemId description is merely 'Value for itemId'.

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 and resource: 'List files/folders inside a OneDrive folder.' It is clear and immediately understandable. However, it does not explicitly distinguish this tool from siblings like list-drive-folder-items or list-my-drive-root-items; the differentiation relies on the tool name rather than the description.

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 about when to use this tool versus alternatives such as list-my-drive-root-items, list-drive-folder-items, or search-my-drive. It simply restates the function without any exclusions, prerequisites, or routing cues, which is a significant gap given the large sibling list.

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