List shared drives

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the bar for additional context is lower. The description adds valuable behavioral context: membership scoping, pagination via nextPageToken, name filtering, and the My Drive exclusion, all beyond what annotations provide.

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 efficient sentences, with the core purpose and output fields front-loaded. Every sentence adds distinct value: scope, downstream usage, filtering, and an exclusion note. No filler or redundancy.

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?

With no output schema, the description appropriately lists the return fields (id, name, createdTime, nextPageToken). It covers pagination, filtering, scope, and how to use the result with sibling tools, making it complete for an agent to call correctly.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that name_contains filters by substring and that the output id is meant to be consumed by search_files or as parent_id, giving the parameters practical usage context.

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 a specific verb ('Lists'), a precise resource ('shared drives'), and the scope ('the authorized user is a member of'), which unambiguously distinguishes it from the sibling tools like search_files or get_file. It further clarifies that My Drive is not included, eliminating a common point of confusion.

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 clear follow-up usage: use the returned drive id as drive_id in search_files or as parent_id to list its root. It also gives an explicit exclusion ('My Drive is not a shared drive and never appears here'), though it does not state when not to use this tool relative to an alternative listing tool.

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