gdrive_list_folder_recursive

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

With no annotations, the description carries the behavioral burden, and it does state the key behavioral trait: recursive traversal through subfolders. It also clarifies the preference for a stable folder_id from search. It stops short of describing error behavior or what happens if neither argument is supplied, but for a read-only listing tool the core behavior is sufficiently disclosed.

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 compact, front-loaded with the purpose, and organized into short labeled sections for args, discovery, and sibling tools. Every line adds information needed to select or invoke the tool correctly.

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 output schema, return values are covered elsewhere, and the description covers argument semantics and alternative tools well. The main remaining gap is that it does not explicitly state whether at least one of folder_name or folder_id is required, despite both being optional in the schema.

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 schema only provides titles and null defaults. The description compensates fully by explaining folder_name with a concrete example, labeling folder_id as optional and preferred when known, and pointing to gdrive_search as the discovery mechanism.

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 opens with a specific verb and resource: 'Recursively list all files in a Google Drive folder and its subfolders.' It explicitly distinguishes itself from gdrive_list_folder for shallow listing, so an agent can immediately tell which tool to use.

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?

It gives clear routing guidance: use gdrive_search first when the folder identifier is unknown, use gdrive_list_folder for shallow listing, and use gdrive_read_file to read a discovered file. This leaves no ambiguity about when to choose this tool over its siblings.

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