gdrive_list_folder

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

No annotations are present, so the description carries the full burden of disclosing behavior. It only states that it lists files, without mentioning whether it includes subfolders recursively, whether folders are included in the output, any permissions needed, or response structure. This is a significant transparency gap for a mutation and listing tool.

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 one concise sentence that conveys the core function without any wasted words. It is appropriately sized for a simple, single-purpose tool.

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?

The tool has one parameter and an output schema exists, so return values do not need explanation. However, the description is minimal and leaves ambiguous whether the listing is recursive or whether subfolders are included, which are important behavioral details for a folder-listing tool. It is minimally viable but not comprehensive.

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 schema covers the only parameter with 100% coverage, and the schema description explains where to obtain the folder_id. The tool description itself adds no parameter-specific details, so the baseline score for high schema coverage is appropriate.

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 clearly states the tool lists all files inside a specific folder, using a specific verb ('List') and resource ('files inside a folder'). It distinguishes itself from generic listing tools like gdrive_list_files by focusing on a folder scope.

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 does not explicitly state when to use this tool versus alternatives like gdrive_list_files or gdrive_search. However, the parameter schema for folder_id mentions 'ID của folder (lấy từ gdrive_list_files)', implying that users should first retrieve a folder ID from gdrive_list_files. This offers weak, implied usage context but no direct exclusion or alternative guidance.

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