microsoft_list_sharepoint_drive_items

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

No annotations are provided, so the description carries full burden. It only states generic routing information (JWT, tenant, company scope) but fails to disclose any specific behavioral traits such as whether this is a read or write operation, pagination behavior, or side effects. The tool's core behavior remains opaque.

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 very short but wastes space on generic boilerplate about routing through /api/tools/invoke, which applies to all connector tools and does not aid in tool selection. The essential information about what the tool does is missing, making it inefficient rather than concise.

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 tool's complexity (listing items in a SharePoint drive) and the presence of similar sibling tools, the description is severely incomplete. It offers no explanation of the required argument structure, no mention of output shape (even though an output schema exists), and no context on drive identification. The agent cannot effectively use this tool based on the given description.

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 single parameter 'arguments' is described only as 'JSON string of arguments for the connector operation' with schema description coverage at 0%. The description adds no value beyond the schema field names; it does not explain what keys or values the JSON should contain (e.g., driveId, itemId). This is entirely insufficient for an agent to invoke the tool correctly.

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 name suggests listing items in a SharePoint drive, but the description merely restates the name as 'Microsoft connector operation list_sharepoint_drive_items' without clarifying what constitutes a 'drive item' or how it differs from sibling tools like microsoft_list_drive_files. The purpose is vaguely inferred 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?

No guidance on when to use this tool versus alternatives. The description provides no context on prerequisites, required inputs, or typical use cases. It only mentions routing details, which are common to all connector tools.

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