gdrive_list_shared_drives

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 behavioral disclosure. It mentions the scope ('visible to the authenticated account') but does not state anything about max_results behavior, pagination, output format, or side effects (though 'List' implies read-only). This leaves significant behavioral gaps for an agent to understand the tool's full behavior.

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 two sentences with no filler. The first sentence front-loads the core purpose, and the second provides actionable sibling guidance. Every word contributes to agent understanding, making it appropriately concise and well-structured.

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 simple list tool with an output schema present, the description is mostly adequate: it states what is listed and how to proceed into shared drives. However, it omits any explanation of max_results or pagination/limit behavior, which is a notable gap for correct invocation. The sibling guidance helps, but the missing parameter semantics keep it from being fully complete.

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 only one parameter (max_results) with 0% schema description coverage. The description does not mention this parameter at all, failing to explain what max_results controls, its default behavior, or how it affects results. No semantic value is added beyond the schema's bare title.

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 ('List') and resource ('Shared Drives') with a clear scope ('visible to the authenticated Google account'). It differentiates from siblings by indicating that folder-level operations happen via gdrive_search/gdrive_list_folder with folder_id values discovered inside a Shared Drive, making the tool's purpose unambiguous.

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 second sentence explicitly names sibling tools as the next step after listing shared drives, providing a clear workflow context. It does not explicitly state when not to use this tool, but the alternative path (use gdrive_search/gdrive_list_folder inside a Shared Drive) is implied, giving adequate usage guidance without exhaustive exclusions.

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