list_files

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

With no annotations, the description carries the full burden and delivers: it discloses UAT-first behavior, the bot limitation (only shared folders), the 403 error for personal-space, the viaUser response field, and the cross-tool token usage. This is significant, non-obvious behavioral information that goes well beyond a simple 'list files' statement.

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?

Two dense sentences pack a lot of useful information. The purpose is front-loaded, and each clause adds value. It is slightly run-on and could be split for readability, but every piece is relevant, so no waste.

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?

Covers purpose, auth-dependent behavior, error conditions, response signal (viaUser), and next-step tool linkage. Missing explicit pagination walkthrough, but the schema covers that. For a tool with no output schema and complex auth semantics, the description is quite 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?

Schema coverage is 100%, so baseline is 3. The description adds meaningful semantic context for folder_token: empty means the UAT user's personal-space root under UAT, and bot contexts behave differently. It also clarifies that the returned token is used with manage_drive_file, though it doesn't elaborate on page_size/page_token beyond the schema.

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+resource: 'List files in a Drive folder.' It clearly distinguishes this from sibling tools like upload_file or manage_drive_file. Additional context about UAT vs bot identity and the personal-space root further clarifies the exact 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?

Provides clear when-to-use context: listing files in a Drive folder, with explicit behavior for UAT vs bot identity and the 403 condition for personal-space folders. It also points to manage_drive_file for next steps. However, it doesn't explicitly name alternatives or say when not to use this tool, which prevents a 5.

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