gdrive_list_files

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

With no annotations, the description fails to disclose key behaviors: it does not state that it is read-only, what happens if Drive is not synced, whether it returns full metadata or just names, or if pagination exists. The scope (locally-synced folder) is vague.

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 a single concise sentence, front-loaded with the verb 'Lists'. Every word adds value, no superfluous information.

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 no parameters or output schema, the description is minimally viable but lacks details on return value format, file/folder information included, and prerequisites like Google Drive sync setup. It is adequate for a simple list operation 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 tool has no parameters; the description implicitly confirms it takes no arguments by stating it lists a fixed path. This is clear enough, though it could specifically say 'No parameters required'.

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 files and folders in Google Drive, specifically the locally-synced folder. It distinguishes from siblings like gdrive_search_files (search) and onedrive_list_files (different service), but could be more explicit that it only lists the root of the synced folder.

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?

No guidance on when to use this tool versus alternatives like gdrive_search_files or finder_list. It does not mention prerequisites (e.g., Google Drive must be synced) or scenarios where this tool is preferred.

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