list_files

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

No annotations provided, so description should allay behavioral concerns. It implies read-only, but lacks details on pagination, rate limits, or what constitutes 'listing' (names, metadata, etc.). Auth is implied via account but not explained.

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?

Single sentence, concise but under-specified. Could benefit from a second sentence covering return format or parameter usage.

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?

With no output schema, no annotations, and low parameter coverage, the description is incomplete. Missing return format, behavior without folder_id, and account authentication details.

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 only 33% (account has description). Description adds no detail beyond enum values for type and optional folder_id. Does not explain how to list root Drive vs. a specific folder.

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 Google Docs or Sheets in Drive or a folder, which distinguishes it from siblings like search_files (which searches content). However, it does not specify what information is returned (e.g., names vs. metadata).

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 vs alternatives like search_files or list_tabs. No mention of prerequisites (e.g., need to connect_google first).

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