List My OneDrive Root

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

With no annotations provided, the description carries the full burden. It clearly indicates a read-only 'List' operation and discloses the specific auth requirement ('Requires delegated Files.Read'). It also specifies the user scope ('signed-in user'), which is valuable. It does not discuss pagination or output format, but these are less critical for a simple list operation.

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 front-loaded with the core purpose, followed by a permission note and a list of Chinese intent examples. The intent list is useful for multilingual agent routing and not excessive. Each sentence serves a distinct purpose, and the overall length is appropriate for the tool's simplicity.

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 tool with one optional parameter and no output schema, the description adequately covers purpose, permission, and user-scope. It could mention that the result is limited to immediate children of the root or the optional top parameter, but those are already implied by the schema and the word 'root'. The Chinese intents enhance contextual completeness for language-driven invocation.

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?

The input schema already covers the only parameter (top) with a clear description and bounds. The tool description adds no additional meaning to the parameter, so the baseline of 3 for high schema coverage is appropriate.

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 action ('List files and folders') and a specific resource ('the signed-in user OneDrive root'), clearly distinguishing it from sibling tools like drive_list_children or drive_search_items. The scope is explicit: root of OneDrive for the signed-in user.

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 implies usage for root-level listing and includes Chinese intent phrases like '查看我的OneDrive' as examples of user queries that should route here. It also states the required permission (delegated Files.Read), providing a prerequisite. However, it does not explicitly contrast with alternatives such as drive_list_children or drive_list_recent.

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