List OneDrive files

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Read-only.' It adds useful behavioral context: default root listing, search fallback, folder-only filtering, and pagination via a previous cursor, all beyond what the annotations provide.

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 compact and front-loaded: the first sentence gives the core purpose and modes, the second covers the onlyFolders filter, and the third covers pagination and read-only nature. Every sentence earns its place with no redundancy.

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 list tool with fully documented parameters and safety annotations, the description covers all invocation paths (root, folder, search, folders-only) and pagination. No output schema exists, but the return shape is evident from 'List files & folders' plus the parameter descriptions.

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?

With 100% schema description coverage, the baseline is 3, but the description adds meaning by defining the root default, the relationship between query and name search, and how pageToken carries pagination state from a previous call. This goes beyond simply restating 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?

States a specific verb ('List') and resource ('files & folders in the user's OneDrive') with clear scope variations: root, folderId, query, and onlyFolders. This distinguishes it from sibling list_drive_files via the OneDrive resource and from get_onedrive_file via the list-vs-get verb.

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?

Provides clear usage context by explaining the root-by-default behavior, folder listing via folderId, name search via query, folder-only filtering, and pagination with pageToken. It does not explicitly name alternatives or exclusions, but the operational modes are unambiguous.

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