Get OneDrive Item

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

No annotations are provided, so the description must carry the transparency burden. It discloses the read-only nature and permission requirements, but does not describe the return format, whether folder metadata differs from file metadata, or any error conditions. This is adequate but not rich.

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 two tight sentences plus an optional Chinese intent helper. It front-loads the primary purpose, includes a key permission detail, and has no filler.

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 read tool with one parameter and no output schema, the description covers the essential context: what it reads, where (signed-in user OneDrive), and the required permission. It lacks explicit return-value details but 'metadata' implies what is returned, making this sufficient for a low-complexity tool.

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 schema already describes the only parameter (itemId as 'OneDrive item ID from a list or search result') with 100% coverage. The description text adds no further parameter context, so the baseline score of 3 applies.

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 ('Read metadata') and clearly identifies the resource ('file or folder in the signed-in user OneDrive'). This distinguishes it from sibling tools like drive_download_file (downloads content) and sharepoint_get_drive_item (uses SharePoint instead of OneDrive).

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 states the required permission ('delegated Files.Read') and implies a read-only usage context. It does not explicitly mention alternatives or when-not-to-use, but the scope is clear enough for an agent to choose this over download or list tools.

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