list_drive_items

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

No annotations are provided, so the description carries the full burden of disclosing behavior. The phrase 'List drive items' implies a read-only operation, but does not mention pagination, sorting, permissions, or return format. It gives minimal behavioral context beyond the name.

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?

While the description is extremely short (three words), this is under-specification rather than conciseness. It omits essential information about parameters, behavior, and return values, so it does not earn its place as a useful tool description.

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?

This is a simple list operation with only two parameters, no output schema, and no annotations. However, even simple tools need more context about what is listed and how filtering works. The description is too sparse to fully support an agent's invocation decisions.

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 description coverage is 0%, and the description does not explain the purpose of 'itemId' or 'driveId' (both of which are strings, with 'driveId' required). The 'itemId' property references '#/properties/driveId', which is confusing. The description adds no semantic meaning beyond the raw schema.

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 ('List') and resource ('drive items'), which clearly indicates a read operation. However, it does not specify what constitutes a drive item (e.g., files, folders) or how this differs from sibling tools like 'list_drives' or 'list_items', leaving some ambiguity.

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?

There is no guidance on when to use this tool versus alternatives like 'list_drives' or 'list_recycle_bin'. The description simply states the action without providing context, prerequisites, or exclusions.

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