List shared drives

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

Adds useful behavior beyond the readOnly/idempotent annotations: omitting account queries every configured account, and the returned canAddChildren field indicates write permission. It also clarifies that shared drives cannot be discovered through drive_search.

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?

Three sentences, front-loaded with the core purpose, and every sentence earns its place. The NOT-a-file clarification, id-resolution role, and account-scoping/output-field note are all necessary and free of repetition.

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?

For a read-only list tool with no output schema, the description still explains the returned ids and canAddChildren field, account selection behavior, and relationship to sibling tools. The main completeness gap is the unresolved conflict between the description and the required account parameter.

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 100%, so the baseline is 3, but the description's claim that omitting account asks every configured account directly contradicts the schema's required: ['account']. This is misleading rather than purely additive. The max_results parameter is left to the schema, which is acceptable.

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?

States a specific action and object: list shared drives and return their ids. It also distinguishes itself from drive_search by clarifying shared drives are not files and never appear in search results, making its role clear.

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?

Clearly explains when to use it: when you need to convert a shared drive name into an id for drive_list, drive_upload, or drive_share. It gives a concrete decision rule by noting that drive_search cannot find shared drives, and it explains account-scoping behavior.

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