List OneDrive Item Permissions

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

The description discloses that it requires delegated Files.Read permission, which is useful. As a list operation, the verb implies read-only behavior, but it does not discuss other behavioral aspects such as response shape, pagination, or handling of empty permission lists.

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 sentences with additional Chinese intents. It is front-loaded with the core action and includes the auth requirement, but the Chinese translation section adds bulk without new information for English agents.

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?

Given the simple one-parameter tool, the description covers the purpose, auth scope, and general resource type. It does not specify return format, but the name and description imply the output is permission metadata; no output schema is present.

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 only parameter itemId is described in the schema as 'OneDrive item ID.' The description reinforces that it applies to a file or folder but adds no further semantics beyond the schema, so the baseline for full schema coverage 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 the specific verb 'List' with resource 'permission and sharing metadata for a file or folder in the signed-in user OneDrive', clearly identifying its scope. The mention of 'signed-in user OneDrive' distinguishes it from the SharePoint permission listing sibling (sharepoint_list_drive_permissions).

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?

No guidance is provided on when to use this tool versus alternatives. It states a required permission (Files.Read) but does not explain scenarios, prerequisites, or exclusions relative to similar tools.

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