List OneDrive files

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Read-only' and explains pagination and search semantics, which are beyond the annotations. It does not contradict annotations and provides useful behavioral context about how the tool operates.

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 three concise sentences with no redundant wording. It front-loads the primary purpose and then covers the key modes and pagination in a logical order. Every sentence earns its place.

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 read-only listing tool, the description covers the necessary modes, pagination, and filtering. It lacks details on error handling or sorting, but these are not critical for a basic list operation. The sibling list_drive_files differentiates Google Drive, and the mention of 'OneDrive' clearly sets the scope.

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 description coverage is 100%, so the parameters are already documented. The description adds value by explaining how the parameters combine (e.g., root vs. folder vs. search, pageToken as cursor) and emphasizes the default behavior. This transcends mere schema repetition.

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 clearly specifies the verb 'list' and the resource 'files & folders in the user's OneDrive', and enumerates three distinct modes (root, folder, search) plus a folders-only filter. This makes it easy to understand what the tool does and how it differs from generic listing 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?

Usage modes are clearly explained: 'root by default', 'folder’s contents (folderId)', 'name search (query)', and pagination with pageToken. It does not explicitly mention alternatives like get_onedrive_file or save_to_onedrive, but the self-contained guidance is sufficient for typical listing use cases.

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