list-my-drive-root-items

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint), so the description does not need to restate that. It adds the useful context that the listing is scoped to the user's OneDrive root and includes both files and folders, though it does not describe return shape or pagination behavior. The schema covers pagination parameters, so this is acceptable.

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 concise sentence with no filler. It front-loads the action and resource, making it easy for an agent 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?

For a simple root-listing tool with fully described optional parameters and robust annotations, the description is mostly complete. It could be slightly richer by noting that subfolders require a different tool, but the core invocation information is sufficient.

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?

All five parameters are already documented in the schema with 100% coverage, so the baseline of 3 applies. The description adds no parameter-specific guidance beyond the resource scope, which is fine but not additive.

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/folders in the root of the user's OneDrive'), making the operation immediately clear. It is distinguishable from sibling tools like list-my-drive-folder-items because it explicitly scopes to the root.

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?

No guidance is given about when to choose this tool over related siblings such as list-my-drive-folder-items or list-drive-root-items. The name and description imply root-level listing, but no explicit selection criteria or exclusions are provided.

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