microsoft_list_sharepoint_drives

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

No annotations are provided, so the description must disclose behavioral traits. It fails to indicate that this is a read-only operation, what aggregation or filtering occurs, or any side effects. The routing details are not behavioral.

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 three sentences. The first identifies the operation, the second provides internal routing details (likely irrelevant for the agent), and the third describes the parameter. It is adequately sized but could be more focused on what the agent needs.

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 presence of an output schema, the description should contextualize what is returned (e.g., list of drives with properties). It does not. Also, with no annotations and a generic wrapper parameter, the description is incomplete for effective tool usage.

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 has a single 'arguments' string parameter with no description. The explanation 'JSON string of arguments for the connector operation' adds minimal value and does not specify what arguments are expected (e.g., site ID, filters).

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 tool name 'list_sharepoint_drives' clearly indicates the verb (list) and resource (sharepoint drives), but the description does not elaborate on what a SharePoint drive is or how it differs from sibling tools like microsoft_list_drive_files or microsoft_list_sharepoint_sites. The purpose is implied but not explicitly stated.

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 provides no guidance on when to use this tool versus alternatives such as microsoft_list_sharepoint_drive_items or microsoft_list_drive_files. There is no mention of prerequisites, scope, or typical use cases.

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