microsoft_list_drive_files

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

No annotations provided. Description only mentions routing and authentication (JWT, tenant, company scope). Lacks info on whether the operation is read-only, pagination, response structure, or any side effects. Output schema exists but description does not hint at return format.

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?

Description is brief but contains redundancy (repeats tool name in first sentence). Front-loads routing details before stating purpose. Could be more streamlined.

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?

Even with output schema, the description fails to specify which drive (OneDrive vs SharePoint), the scope of files listed, or any filtering options. Incomplete for a file listing 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?

Schema coverage is 0%. The description merely restates the parameter name and type ('JSON string of arguments') without explaining what keys/values are expected inside the JSON. Does not help the agent construct valid arguments.

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 it lists drive files, but does not specify whether it covers OneDrive, SharePoint, or both. The sibling tool 'microsoft_list_sharepoint_drive_items' exists, but the description does not differentiate. Purpose is somewhat vague.

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 on when to use this tool versus other Microsoft listing tools like microsoft_list_sharepoint_drive_items or microsoft_list_emails. The agent is left to infer context 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.