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 it does disclose one real behavioral trait: folder_id restricts to direct children, i.e. the listing is non-recursive. It omits permissions/auth requirements, pagination and rate-limit behavior, and the fact that trashed files are excluded by default.

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?

Three compact sentences with the core purpose front-loaded, then query syntax, then folder scoping. The inline example is the only slightly heavy element, though it earns its place by showing the exact dialect.

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?

For a 4-parameter search tool with no output schema and no annotations, the description covers half the parameters and one behavioral constraint. It leaves the agent without any sense of the result shape, ordering, or how the 50-default/200-max result cap interacts with paging.

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 50% (query and folder_id described, max_results and include_trashed undocumented). The description adds genuine meaning for `query` by naming the Drive query dialect and giving a concrete compound predicate, and clarifies folder_id as non-recursive, but contributes nothing for the two uncapped/undocumented parameters.

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?

States a specific verb pair (list/search) and resource (files), which an agent can distinguish from read_file/get_file/create_file siblings by the act of enumerating rather than fetching a known file. It stops short of explicitly naming those siblings or stating the boundary between searching and fetching.

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 when-to-use guidance and no explicit alternative; the agent must infer that this is the enumeration counterpart to get_file/read_file. Nothing tells it when searching is preferable to directly retrieving a known file, nor when folder scoping is appropriate versus a query.

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