list-drive-root-items

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no further behavioral context such as truncation, continuation, non-recursive listing, or default ordering; it only restates the resource scope.

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. The parenthetical '(document library)' earns its place by disambiguating the term 'drive' in the Microsoft Graph context.

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?

As a read-only list tool with well-documented parameters and informative annotations, the definition is minimally viable. However, it omits any mention of when to use this over sibling list tools, and with no output schema the agent receives no guidance on return shape or pagination beyond what the maxItems parameter description already states.

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 baseline of 3 applies. The tool description itself adds no parameter-level meaning beyond what the schema already provides for driveId, cursor, filter, select, orderby, and maxItems.

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 uses a specific verb ('List') and a specific resource ('files/folders in the root of a drive'), and clarifies that 'drive' means a document library. It is unambiguous, but it does not explicitly distinguish itself from sibling tools like list-drive-folder-items or list-my-drive-root-items, so differentiation relies mostly on the tool name.

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 on when to use this tool versus alternatives such as list-drive-folder-items or list-my-drive-root-items. There are no explicit conditions, exclusions, or references to sibling tools, leaving the agent to infer usage from the name alone.

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