gdrive_list

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

Without annotations, the description only states 'List files and folders', implying a read-only operation. It does not explicitly disclose whether it modifies data, rate limits, or permission requirements. The behavior is clear but not fully detailed.

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 that immediately conveys the tool's purpose without unnecessary words.

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 description does not explain the return format (e.g., file/folder metadata, pagination) or error conditions. Given no output schema, this leaves the agent lacking critical information for correct invocation.

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 coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., parentId and pageSize descriptions already exist).

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 a specific directory or root folder, matching the verb 'list' and resource 'files and folders'. It distinguishes itself from siblings like gdrive_search (which searches across drives) and gdrive_read_file (which reads a single file).

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 (e.g., gdrive_search). The description lacks context about prerequisites or decision criteria for selection.

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